Generate client from secured WSDL URL

I was playing arounf with the (excellent) Web Service Proxy generation wizard in JDeveloper.
It works great but I did run into one annoying issue.
When I try to enter an URL to a WSDL that will serve as the source for the proxy generation JDeveloper is not able to find it if the URL requires some form of authentication. In my example the service requires basic username/password authentication (and so does the ?WSDL).
I can work around it by accessing the WSDL through my browser and storing it locally but I'd prefer to use the direct URL so that I can easily refresh it. Is there something I'm doing wrong?

Thanks for the assistance, I've saved the WSDL locally and secured the proxy, now I get the following error :
SEVERE: No username found
Exception in thread main
oracle.j2ee.ws.common.soap.fault.SOAP11FaultException: No username found
at oracle.security.wss.interceptors.AbstractSecurityInterceptor.throwSOAPFaultException(AbstractSecurityInterceptor.java:222)
at oracle.security.wss.interceptors.AbstractSecurityInterceptor.handleOutbound(AbstractSecurityInterceptor.java:196)
at oracle.security.wss.interceptors.ClientInterceptor.handleRequest(ClientInterceptor.java:48)
at oracle.j2ee.ws.common.mgmt.runtime.InterceptorChainImpl.handleRequest(InterceptorChainImpl.java:122)
at oracle.j2ee.ws.common.mgmt.runtime.AbstractInterceptorPipeline.handleRequest(AbstractInterceptorPipeline.java:87)
at oracle.j2ee.ws.client.StubBase._preRequestSendingHook(StubBase.java:646)
at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java:141)
at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:111)
at testsms.runtime.Service1Soap_Stub.ws_submitSimple(Service1Soap_Stub.java:453)
at testsms.Service1SoapClient.ws_submitSimple(Service1SoapClient.java:52)
at testsms.Class1.main(Class1.java:41)
Caused by: FAULT CODE: InvalidSecurity FAULT MESSAGE: No username found
at oracle.security.wss.WSSecurity.build(WSSecurity.java:1627)
at oracle.security.wss.interceptors.AbstractSecurityInterceptor.handleOutbound(AbstractSecurityInterceptor.java:188)
... 9 more
The only thing I enabled when securing it was Authentication, when I right click and edit the security propertes the "Authentication" tab has "Use Username to Authenticate" password type "Plain text" and I disabled "Add Nonce" and "Add create time" after it failed first time.
Where is it expecting to get username and password from ? I have the right username and apssword in Tools->Preferences->Web Browser and Proxy, is that where it comes from ?
Just to reitterate its the internet proxy server at my end that I'm trying to get through - the web service itself does not use WS Security, so I'm thinking that the mention of WSSecurity in the error means I'm going the wrong way here.

Similar Messages

  • Xrpcc: Generate stub from existing WSDL

    Hi, I have an error when generating stub from existing WSDL using xrpcc tool.
    Anyone know what is the problem? Thanks!
    The error message:
    warning: ignoring operation "registration": more than one part in input message
    warning: ignoring operation "checkRegistration": more than one part in input message
    warning: Port "AccountManagementService" does not contain any usable operations
    warning: ignoring operation "registration": more than one part in input message
    warning: ignoring operation "checkRegistration": more than one part in input message
    warning: Port "AccountManagementService" does not contain any usable operations
    Note: sun.tools.javac.Main has been deprecated.
    1 warning
    The WSDL file:
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions
    name="serverone.paymentofgovbill.service.useraccount.AccountManagementService"
    targetNamespace="urn:serverone.paymentofgovbill.service.useraccount.AccountManagementService"
    xmlns:map="http://systinet.com/mapping/"
    xmlns:ns0="http://systinet.com/xsd/SchemaTypes/"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:tns="urn:serverone.paymentofgovbill.service.useraccount.AccountManagementService"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    <wsdl:types>
    <xsd:schema targetNamespace="http://systinet.com/xsd/SchemaTypes/"
    elementFormDefault="qualified"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:tns="http://systinet.com/xsd/SchemaTypes/"
    xmlns:map="http://systinet.com/mapping/"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:ns0="http://systinet.com/xsd/SchemaTypes/"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    <xsd:element name="p0" type="xsd:string" nillable="true"/>
    <xsd:element name="p1" type="xsd:string" nillable="true"/>
    <xsd:element name="string_Response" type="xsd:string"
    nillable="true"/>
    <xsd:element name="int_Response" type="xsd:int"/>
    </xsd:schema>
    </wsdl:types>
    <wsdl:message name="AccountManagementService_registration_1_Request">
    <wsdl:part name="p0" element="ns0:p0"/>
    <wsdl:part name="p1" element="ns0:p1"/>
    </wsdl:message>
    <wsdl:message name="AccountManagementService_checkRegistration_1_Request">
    <wsdl:part name="p0" element="ns0:p0"/>
    <wsdl:part name="p1" element="ns0:p1"/>
    </wsdl:message>
    <wsdl:message name="AccountManagementService_checkRegistration_Response">
    <wsdl:part name="response" element="ns0:int_Response"/>
    </wsdl:message>
    <wsdl:message name="AccountManagementService_registration_Response">
    <wsdl:part name="response" element="ns0:string_Response"/>
    </wsdl:message>
    <wsdl:portType name="AccountManagementService">
    <wsdl:operation name="registration" parameterOrder="p0 p1">
    <wsdl:input
    message="tns:AccountManagementService_registration_1_Request"/>
    <wsdl:output
    message="tns:AccountManagementService_registration_Response"/>
    </wsdl:operation>
    <wsdl:operation name="checkRegistration" parameterOrder="p0 p1">
    <wsdl:input
    message="tns:AccountManagementService_checkRegistration_1_Request"/>
    <wsdl:output
    message="tns:AccountManagementService_checkRegistration_Response"/>
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="AccountManagementService"
    type="tns:AccountManagementService">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http"
    style="document"/>
    <wsdl:operation name="registration">
    <map:java-operation name="registration"
    signature="KExqYXZhL2xhbmcvU3RyaW5nO0xqYXZhL2xhbmcvU3RyaW5nOylMamF2YS9sYW5nL1N0cmluZzs="/>
    <soap:operation
    soapAction="urn:serverone.paymentofgovbill.service.useraccount.AccountManagementServiceAccountManagementService#registration#KExqYXZhL2xhbmcvU3RyaW5nO0xqYXZhL2xhbmcvU3RyaW5nOylMamF2YS9sYW5nL1N0cmluZzs="
    style="document"/>
    <wsdl:input>
    <soap:body use="literal"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="checkRegistration">
    <map:java-operation name="checkRegistration"
    signature="KExqYXZhL2xhbmcvU3RyaW5nO0xqYXZhL2xhbmcvU3RyaW5nOylJ"/>
    <soap:operation
    soapAction="urn:serverone.paymentofgovbill.service.useraccount.AccountManagementServiceAccountManagementService#checkRegistration#KExqYXZhL2xhbmcvU3RyaW5nO0xqYXZhL2xhbmcvU3RyaW5nOylJ"
    style="document"/>
    <wsdl:input>
    <soap:body use="literal"/>
    </wsdl:input>
    <wsdl:output>
    <soap:body use="literal"/>
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="AccountManagementService">
    <wsdl:port name="AccountManagementService"
    binding="tns:AccountManagementService">
    <soap:address
    location="http://localhost:6060/AccountManagementService/"/>
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>

    The JAXRPC spec. section 6.2 states:
    "All message parts (either parameter or return value) appear inside a single wrapper element, which is the first child element of the SOAP Body element." For this to work with Doc/literal operations, all messages can contain only a single part.

  • Webservice Client with Secure WSDL?

    I have a WSDL which is user id and password protected. How do I generate the web services client for this secure wsdl?
    weblogic clientgen ant task doesn't seem to accept the user id and password.
    Any suggestions? Appreciate your help.

    Thanks YoGee for your response.
    I generated the client jar with the physical copy of wsdl but the problem is while accessing the web service, the client code doesn't find the wsdl.
    Here is the sample code
    HelloWS_Service helloService = new HelloWS_Service(
                                   new URL("http://100.100.0.88/axis/services/HelloWS?wsdl"),
                                   new QName("http://test.ap.com","HelloWS"));
    // Is there a way I could pass username and password to access  the wsdl?
    HelloWSService helloWS = helloService.getHelloWSPort();The exception occurs while reading the Web Service
    javax.xml.ws.WebServiceException: weblogic.wsee.wsdl.WsdlException:
             Failed to read wsdl file from url due to -- java.io.IOException:
             Server returned HTTP response code: 401 for
             URL: http://100.100.0.88/axis/services/HelloWS?wsdl
             at weblogic.wsee.jaxws.spi.WLSProvider.readWSDL(WLSProvider.java:306)Edited by: munnar on Jun 15, 2010 8:06 AM

  • Error creating a web service client from th WSDL document (soamanager)

    Hello everyone,
    we have generate with the wizard a web-service using the function module BAPI_CONTROL_RECIPE_GET_LIST. Then we have generated with SOAMANAGER the end point. As test, we have used a web-service explorer of Eclispe and we can retrieve without problems the data.
    Then we wanted to generate the web-servcie client with Eclipse Galileo (3.5.0) wiith the server GlassFish v2.1 Java EE 5 we first installed the WSIT jars, in order to support WS-RM protocol
    We have started the generation based on the document obtainend within the soamanager under the "Open WSDL document for selected binding" link.
    We have tried it several times and we always got the following error is:
    IWAB0399E Error in generating Java from WSDL: WSDLException (at /wsdl:definitions/wsdl:portType/wsp:Policy):
    faultCode=INVALID_WSDL: Encountered unexpected element 'Policy'.: <br>
        WSDLException (at /wsdl:definitions/wsdl:portType/wsp:Policy): faultCode=INVALID_WSDL: Encountered unexpected element 'Policy'.:
    at com.ibm.wsdl.util.xml.DOMUtils.throwWSDLException(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.parsePortType(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
    at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
    at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:516)
    at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)
    at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
    at java.lang.Thread.run(Unknown Source)
    Do you know if we took the right document in order to generate the web-service client? Do we need to have some specifics settings in the configurations of th endpoint? (provider security, transport settings, etc...?)
    If needed, or if someone would be nice enough to try to generate it on its side, I can post here the whole wsdl document, but due to its length, I first wait your comments.
    Thanks a lot in advance for your feed-back
    best regards
    Pierre-André
    addtions:
    maybe this should have been better posted within the forum Service-Oriented Architecture than standards?
    I forgot to mention the following threads, which seems to me to be somehow in this direction. But I do not get really how I could use them, or how is is releated.
    Edited by: Pierre-andre Jacquod on Sep 23, 2009 4:02 PM

    Hi,
    I am facing the same issue while generating the client java class from IBM RAD 6.0.
    Here is the error I am getting.
    WSDLException (at /wsdl:definitions/wsdl:portType/wsp:Policy): faultCode=INVALID_WSDL: Encountered unexpected element 'Policy'.:
         [java] at com.ibm.wsdl.util.xml.DOMUtils.throwWSDLException(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parsePortType(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.parseDefinitions(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
         [java] at com.ibm.wsdl.xml.WSDLReaderImpl.readWSDL(Unknown Source)
         [java] at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:516)
         [java] at org.apache.axis.wsdl.symbolTable.SymbolTable.populate(SymbolTable.java:495)
         [java] at org.apache.axis.wsdl.gen.Parser$WSDLRunnable.run(Parser.java:361)
         [java] at java.lang.Thread.run(Thread.java:571)
    Please guide me to resolve this issue.
    Thanks & Regards,
    Vijay

  • How to create a Java Client from a wsdl file...

    Hi,
    I am looking for an available option for calling a Cobol unit from a Java application( front end). I've used the MicroFocus tool for creating a wsdl file from our Cobol unit.. Now i want to use this wsdl file for creating a Java Client..
    Can any one suggest a suitable solution (software that makes use of the already existing wsdl file and generate a Java Client for that) ASAP....
    Thanks,
    roopa

    Hey you can create java client using Eclispe or WSAD or far that matter any other IDE. crate a project save the WSDLs in a package. Right click on WSDL goto webservice option. From there you can generate client.
    cheers,
    sapan
    Is it still open ?
    cheers,
    sapan
    Edited by: sapan on Feb 25, 2009 1:17 AM

  • [Eclipse - Axis] Generate Client from wsld, wrong type for unbounded elemen

    Hi all!
    I'm not expert on wsdl format, but in my work activities I have to take wsdl they send to me and generate Java code in Eclipse.
    One of last wsdl they sent to me contains the following element:
    <xs:element ref="ns0:CodicePraticaDistributore" minOccurs="0" maxOccurs="unbounded"/>where ns0:CodicePraticaDistributore is:
    <xs:element name="CodicePraticaDistributore" type="ns0:CodPratica"/>and ns0:CodPratica is:
    <xs:simpleType name="CodPratica">
         <xs:restriction base="xs:string">
              <xs:maxLength value="15"/>
         </xs:restriction>
    </xs:simpleType>(Sorry I don't report whole wsdl... but it's VERY long!)
    When I do right click on the wsdl and follow Web Services - Generate Client and so on... the generated class contain following lines:
    elemField.setXmlName(new javax.xml.namespace.QName("http://xmlns.a2a.eu/Unbundling/documentum/schema/DocumentalePrestazione", "CodicePraticaDistributore"));
    elemField.setXmlType(new javax.xml.namespace.QName("http://xmlns.a2a.eu/Unbundling/documentum/schema/DocumentalePrestazione", "CodicePraticaDistributore"));Which are wrong, 'cause the second argument for setXmlType should be CodPratica and not CodicePraticaDistributore.
    The right one should be:
    elemField.setXmlName(new javax.xml.namespace.QName("http://xmlns.a2a.eu/Unbundling/documentum/schema/DocumentalePrestazione", "CodicePraticaDistributore"));
    elemField.setXmlType(new javax.xml.namespace.QName("http://xmlns.a2a.eu/Unbundling/documentum/schema/DocumentalePrestazione", "CodPratica"));This makes Axis generate wrong xml, with addition of xsi:type="xsd:string" which makes the other system (where I send xml) to return me an error for bad xml format.
    The generated xml code for this data is:
    <CodicePraticaDistributore xsi:type="xsd:string">PN100000000110E</CodicePraticaDistributore>While it should be simply:
    <CodicePraticaDistributore>PN100000000110E</CodicePraticaDistributore>I can't understand how to resolve this behaviour on Java generation (other than modifying the final generated Java Class).
    Can you help me?

    I didn't meant to "up" again the topic... I was just marking it as "resolved" to remove from "unresolved" topics in my control panel... but it asked to me if I wanna add a comment... I didn't guess it would be post in the topic and up it again, sorry.
    I also tried in the API forum, but no answer neither there.
    I tried Axis2, but at the end I found some incompatibilites, because in the project I'm working on there are lot of wsdl, but only this one generate the said problem.
    But them all write in the same paths, and this generates case-sensitive problems on paths (under windows).
    At the end I simply think they left Axis1 as it is (whith this bug included), and they're only on Axis2... which is not so compatible with Axis1.
    So up to now no solution, if not edit manually the error... or rewrite the whole project for classes generated by another wsdlToJava generator (which is a HUGE work).
    Thank you anyway. :)

  • JAX WS generated client for Contact WSDL V2.0 is not working

    Hi,
    I have generated stubs for Contact WSDL v2.0 using Metro JAX WS tool. I tried to use the generated stubs but was failed.
         Contact_Service service = new Contact_Service();
         Contact contService = service.getContact();
         BindingProvider bp = (BindingProvider) contService;
         Map<String, Object> context = bp.getRequestContext();
         context.put(BindingProvider.ENDPOINT_ADDRESS_PROPERTY, sessionEndPoint);
    The execution of service.getContact() statement completes in approx 15-20 mins with the below exception stack trace:
         Thread [main] (Suspended (exception InvocationTargetException))     
              GeneratedConstructorAccessor22.newInstance(Object[]) line: not available     
              DelegatingConstructorAccessorImpl.newInstance(Object[]) line: 27     
              Constructor<T>.newInstance(Object...) line: 513     
              PropertyFactory.create(JAXBContextImpl, RuntimePropertyInfo) line: 113     
              ClassBeanInfoImpl<BeanT>.<init>(JAXBContextImpl, RuntimeClassInfo) line: 164     
              JAXBContextImpl.getOrCreate(RuntimeClassInfo) line: 479     
              JAXBContextImpl.<init>(JAXBContextImpl$JAXBContextBuilder) line: 305     
              JAXBContextImpl$JAXBContextBuilder.build() line: 1100     
              ContextFactory.createContext(Class[], Collection<TypeReference>, Map<Class,Class>, String, boolean, RuntimeAnnotationReader, boolean, boolean, boolean) line: 143     
              JAXBRIContext.newInstance(Class[], Collection<TypeReference>, Map<Class,Class>, String, boolean, RuntimeAnnotationReader) line: 95     
              JAXBContextFactory$1.createJAXBContext(SEIModel, List<Class>, List<TypeReference>) line: 97     
              AbstractSEIModelImpl$1.run() line: 148     
              AbstractSEIModelImpl$1.run() line: 140     
              AccessController.doPrivileged(PrivilegedExceptionAction<T>) line: not available [native method]     
              SOAPSEIModel(AbstractSEIModelImpl).createJAXBContext() line: 140     
              SOAPSEIModel(AbstractSEIModelImpl).postProcess() line: 83     
              RuntimeModeler.buildRuntimeModel() line: 244     
              WSServiceDelegate.createSEIPortInfo(QName, Class, WebServiceFeature...) line: 687     
              WSServiceDelegate.addSEI(QName, Class, WebServiceFeature...) line: 675     
              WSServiceDelegate.getPort(WSEndpointReference, QName, Class<T>, WebServiceFeature...) line: 330     
              WSServiceDelegate.getPort(QName, Class<T>, WebServiceFeature...) line: 313     
              WSServiceDelegate.getPort(QName, Class<T>) line: 295     
              Contact_Service(Service).getPort(QName, Class<T>) line: 99     
              Contact_Service.getContact() line: 72     
              Main.main(String[]) line: 25     
    I have also generated stubs for Contact WSDL v1 using JAX-WS and it was working fine.
    I am wondering why JAX-WS stubs for Contact WSDL V2 is not working. I have also generated stubs for both v1 and v2 WSDL using Axis tool, and it was working fine.
    Can anyone suggest us the workaround/solution to this issue.
    Thanks for your patients and time.
    Regards
    Ravish

    Hello Ravish,
    Can you please confirm the following:
    1) Check the Admin>Web Services Utilization page in CRMOD to see if the request is received
    2) Do you receive any response from CRMOD on the client side and if so, please post the SOAP response
    3) Have you tried other objects and had any issues with them?
    Thanks,
    Sean

  • How to Create WebService (the Server, not Client) from existing WSDL

    Does anyone have any suggestions on how to create a WebService from existing WSDL.  I have been asked to implement a WebService (the Server) based on WSDL from a standards based consortium.  I have created several WebServices in the past and the generated WSDL under my control.  Does Axis WebServices generate WebService service stub Java code?

    Hai
      you can create stubs for AXis webservices also
      for help use the following link
    http://www.onjava.com/pub/a/onjava/2002/06/05/axis.html?page1

  • Generating proxies from WSDL utility

    Hey ..
    Does BEA give a utility to generate client webservice proxy classes from a WSDL
    I mean ..instead of any server classes to run clientgen..I have just the WSDL
    and I need to generate the proxy classes for myself..I guess it defeats the purpose
    of webservices(integration)..if I have to ask the webservice deployer for client
    classes ..!
    Thanx,
    Krish

    "Krishnan Venkataraman" <[email protected]> wrote in message
    news:[email protected]...
    >
    Manoj , u sure this is a valid link ...coz I cannot see a wsdl athttp://example.com/myapp/myservice.wsdl..
    This should be the url to your wsdl. (the wsdl from which you want
    to generate the service). You can also copy the wsdl to your local
    machine and use the file url.
    >
    and is there any WLS70 dependency for me to generate these proxies ...Imean do
    I need anything from WLS70 (jar files etc)for me to do this task ...?You need wls70. the clientgen ant task is provided by wls70.
    >
    BTW.. just to update u on our other issue we talked about...have a look atthe
    below trace...Thanx,Krish
    Shridhar ...
    Couple of things ...
    1) We will ask the webservice provider put the CR080927_70sp1.jar intheir classpath.
    But instead of they generating the client-jar and runningVersionMaker on
    this to give us the output , can we do this on ourside...
    I understand that there is a way in which the client itself generatestheir
    own proxies from the wsdl...In case we can do this ...isCR080927_70sp1.jar required
    on
    the client side also for generating the proxies...or is it required onthe
    WLS70 side only at runtime...once we generate these proxies ourselves thenfor
    compiling our 6.0 client and running it , I will use the output ofversionMaker
    and wsclient70.jar.
    2) Can u possibly mail me the patched jar files which u mention below byemail...and
    send me a confirmation email saying u have sent it..coz we seem to havesome firewall
    issues going to an outside ftpserver....and the confirmation mail is onlyincase
    u send the mail and I do not get it coz of the size etc ..
    Thanx,
    Krish
    Krishnan (Krish) Venkataraman
    Bank of America Corp.
    Senior Technology Analyst
    Email: [email protected]
    Work # : 646 733 4248
    Cell # : 646 210 5482
    -----Original Message-----
    From: Shridhar Mysore [mailto:[email protected]]
    Sent: Friday, November 01, 2002 12:38 PM
    To: Venkataraman, Krishnan
    Subject: Invoking 7.0 WS from 6.0 WS client [ Case 367229 ]
    Hello Krishnan,
    Firstly, your present configuration (involving the use of a SessionBeanin 6.0sp1
    as WS client calling into a WS hosted in 7.0sp1) where you are using 7.0webserviceclient.jar
    alongside 6.0 weblogic.jar is not supported, nay non-viable. The result ofsuch
    a configuration would lead to NoSuchMethodError exceptions which you haveseen
    at your end.
    Secondly, in order to solve this we need to use portable stubs for WSclients,
    a feature, that has been included in
    7.0 SP02 ! We, however have made this feature available on 7.0 SP01 aswell in
    the form of a one-off patch !
    And the following is a procedure for enabling this on 7.0SP01 :
    - Add the one-off patch ( CR080927_70sp1.jar ) at the beginning of theCLASSPATH
    in your 7.0 server startup script. Ensure that you restart the server forthis
    to kick in.
    - Generate the client jar for the 7.0 WS
    - Run the weblogic.webservice.tools.versioning.VersionMaker utility bysupplying
    the client jar to generate re-versioned classes.
    - Compile the WS client in 6.0 by supplying the re-versioned classes(generated
    from VersionMaker ) and wsclient70.jar (note wsclient70.jar should workwith
    6.x versions)
    - Run the WS client in 6.0 by supplying the re-versioned classes(generated from
    VersionMaker ) and wsclient70.jar
    Lastly, please find/download the following files from our FTP server(ftpsupport.beasys.com)
    at /pub/case367229
    by logging in with username/password as support/pechool
    ( Note : this password is valid for the week of Oct 27, 2002 )
    CR080927_70sp1.jar - one-off patch for 7.0sp01
    wsclient70.jar - this would be used instead ofwebserviceclient.jar by
    6.x WS client/s
    "manoj cheenath" <[email protected]> wrote:
    Sure. you can generate client from a WSDL.
    Please try this:
    <clientgen wsdl="http://example.com/myapp/myservice.wsdl"
    packageName="myapp.myservice.client"
    clientJar="c:/myapps/myService_client.jar"/>
    regards,
    -manoj
    "Krishnan Venkataraman" <[email protected]> wrote in message
    news:[email protected]...
    Hey ..
    Does BEA give a utility to generate client webservice proxy classesfrom a
    WSDL
    I mean ..instead of any server classes to run clientgen..I have justthe
    WSDL
    and I need to generate the proxy classes for myself..I guess it defeatsthe purpose
    of webservices(integration)..if I have to ask the webservice deployerfor
    client
    classes ..!
    Thanx,
    Krish

  • How to generate doc/lit/wrapped services from existing wsdl?

    Hello,
    I am using workshop 10.1 to generate webservices from existing wsdl files from workshop 8.1. The existings webservices are based on an xmlbean utility project.
    When I generate the webservice from the existing wsdl file it generates automatically services with doc/lit/bare operations. I found in the known issues that this combination is not supported in combination with xmlbeans.
    See: CR283457
    XBeans are not supported as parameters or return type for doc/lit/bare operations.
    Use of Xbeans as a parameter or return type with doc/lit/bare bindings is not supported in operations or callbacks and will result in a failure during deployment.
    Platform: All
    Workaround: Use doc/lit/wrapped for services that use XBeans as parameters or return types.
    The workaround state to use doc/lit/wrapped for services. My questions is how to do that since workshop has all control over the generation of the webservices? ?:|
    Thanks in advance,
    Martijn Baels
    Software Architect
    www.leanapps.com

    Hi Martijn
    If you do generate web service from the wsdl on a 9.2 project, it always uses jax-rpc types and there's no xmlbeans involved.
    If the wsdl is in the schemas folder and the xmlbeans builder is on, then you also have xmlbeans types created by the builder they aren't being used by the web service. You will still have problems, because some of the xmlbeans types may conflict with the jax-rpc types.
    so when we generate webservice from a wsdl it will never use xmlbeans type, even if the xml builder is on, because WLS doesn't support start from wsdl with xmlbeans types.
    Can you please attach the wsdl and the steps so I can replicate and see the issue?
    Thanks
    Vimala

  • Weblogic 8.1 :: Getting error while generating Client java class from WSDL

    Hi,
    For SOAP webservice, I am using ant script to generate java client from WSDL but getting below error. Please inform if any suggestion to resolve this.
    Also let me know if any other alternative to generate client java code.
    Ant script:
    ===========
    <project name="project" default="generateClientJar">
         <property file="build.property">
         </property>
         <taskdef name="clientgen" classname="weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask">
              <classpath>
                   <fileset dir="${build_lib.dir}" includes="*.jar" />
              </classpath>
         </taskdef>
         <path id="compile_path">
              <pathelement location="C:/jar/wls-api.jar" />
              <pathelement location="${build_lib.dir}/weblogic.jar" />
              <pathelement location="C:/jar/webserviceclient+ssl.jar" />
              <pathelement location="D:/Java_Src_10.1.0/nextgen_arch/wlpatch/webservices.jar" />
         </path>
         <target name="generateClientJar" depends="generate.client">
    <clientgen wsdl="${wsdl.file}" classpathref="compile_path"
    serviceName="${service.name}"
    packageName= "${client.pkg}"
    clientJar="${ws.client.name}" />
         </target>
         <target name="generate.client" description="Generate web-services client">
              <property name="wsdl.file" value="${sms.wsdl.file}"/>
              <property name="client.pkg" value="${sms.client.pkg}"/>
              <property name="ws.client.name" value="${ws.sms.name}"/>
              <property name="service.name" value="${sms.service.name}"/>
         </target>
    </project>
    build.property file
    ===========
    base=C:/SMS
    lib=E:/jar_path
    sms.wsdl.file=${base}/SMS.wsdl
    sms.client.pkg=com.db.dbdi.gtbportal.sms.client     
    ws.sms.name=${lib}/ws_SmsService_client.jar
    sms.service.name=SMSService
    build_lib.dir = E:/jar_path
    Error log:
    ================
    Buildfile: D:\Java_Src_10.1.0\ant\build_weblogic8.xml
    generate.client:
    generateClientJar:
    [clientgen] Generating client jar for C:/SMS/SMS.wsdl ...
    [clientgen] C:\Documents and Settings\amitkumar.patel\Local Settings\Temp\ws_SmsService_client.jar699419996\com\db\dbdi\gtbportal\sms\client\SMSPort.java:15: parameters is already defined in sendSMS(com.db.portal.webservices.sms.SendSMS,com.db.portal.webservices.sms.holders.SendSMSResponseHolder)
    [clientgen] public void sendSMS(com.db.portal.webservices.sms.SendSMS parameters, com.db.portal.webservices.sms.holders.SendSMSResponseHolder parameters)
    [clientgen] ^
    [clientgen] C:\Documents and Settings\amitkumar.patel\Local Settings\Temp\ws_SmsService_client.jar699419996\com\db\dbdi\gtbportal\sms\client\SMSPort.java:21: parameters is already defined in getStatus(com.db.portal.webservices.sms.GetStatus,com.db.portal.webservices.sms.holders.GetStatusResponseHolder)
    [clientgen] public void getStatus(com.db.portal.webservices.sms.GetStatus parameters, com.db.portal.webservices.sms.holders.GetStatusResponseHolder parameters)
    [clientgen] ^
    [clientgen] C:\Documents and Settings\amitkumar.patel\Local Settings\Temp\ws_SmsService_client.jar699419996\com\db\dbdi\gtbportal\sms\client\SMSPort_Stub.java:20: parameters is already defined in sendSMS(com.db.portal.webservices.sms.SendSMS,com.db.portal.webservices.sms.holders.SendSMSResponseHolder)
    [clientgen] public void sendSMS(com.db.portal.webservices.sms.SendSMS parameters, com.db.portal.webservices.sms.holders.SendSMSResponseHolder parameters)
    [clientgen] ^
    [clientgen] C:\Documents and Settings\amitkumar.patel\Local Settings\Temp\ws_SmsService_client.jar699419996\com\db\dbdi\gtbportal\sms\client\SMSPort_Stub.java:39: parameters is already defined in getStatus(com.db.portal.webservices.sms.GetStatus,com.db.portal.webservices.sms.holders.GetStatusResponseHolder)
    [clientgen] public void getStatus(com.db.portal.webservices.sms.GetStatus parameters, com.db.portal.webservices.sms.holders.GetStatusResponseHolder parameters)
    [clientgen] ^
    [clientgen] Note: C:\Documents and Settings\amitkumar.patel\Local Settings\Temp\ws_SmsService_client.jar699419996\com\db\dbdi\gtbportal\sms\client\SMSService.java uses or overrides a deprecated API.
    [clientgen] Note: Recompile with -deprecation for details.
    [clientgen] 4 errors
    *[*clientgen] java.io.IOException: Compiler failed executable.exec**
    [clientgen] at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(CompilerInvoker.java:470)
    [clientgen] at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:328)
    [clientgen] at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvoker.java:336)
    [clientgen] at weblogic.webservice.tools.build.internal.CompilerHelper.compileFiles(CompilerHelper.java:80)
    [clientgen] at weblogic.webservice.tools.build.internal.ClientGenImpl.compileStubs(ClientGenImpl.java:627)
    [clientgen] at weblogic.webservice.tools.build.internal.ClientGenImpl.generateStub(ClientGenImpl.java:572)
    [clientgen] at weblogic.webservice.tools.build.internal.ClientGenImpl.doClientGenFromWsdl(ClientGenImpl.java:409)
    [clientgen] at weblogic.webservice.tools.build.internal.ClientGenImpl.run(ClientGenImpl.java:340)
    [clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.doClientGen(ClientGenTask.java:351)
    [clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(ClientGenTask.java:208)
    [clientgen] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
    [clientgen] at org.apache.tools.ant.Task.perform(Task.java:364)
    [clientgen] at org.apache.tools.ant.Target.execute(Target.java:341)
    [clientgen] at org.apache.tools.ant.Target.performTasks(Target.java:369)
    [clientgen] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
    [clientgen] at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
    [clientgen] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:40)
    [clientgen] at org.eclipse.ant.internal.ui.antsupport.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:32)
    [clientgen] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
    [clientgen] at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.run(InternalAntRunner.java:423)
    [clientgen] at org.eclipse.ant.internal.ui.antsupport.InternalAntRunner.main(InternalAntRunner.java:137)
    BUILD FAILED
    D:\Java_Src_10.1.0\ant\build_weblogic8.xml:34: weblogic.webservice.tools.build.WSBuildException: Compiler failed executable.exec - with nested exception:
    [java.io.IOException: Compiler failed executable.exec]
    Total time: 1 minute 12 seconds

    Hi,
    Can u Please post the WSDL..here. I remember long back i resolved this kind of issue...when i was getting "*parameters is already defined in - - -*" while using ClientGen.
    Once i will get the WSDL may be i can recall it...
    If u have any problem in Posting the WSDL..in Forums .. then let me know I will send my E-Mail Address...
    As far as i remember ..it usually happens when we Run ClientGen task of WLS81 ON the WebService/WSDL generated by WebLogic 9.x or Above. Please let me know if this is the Case with you as well... . I remember there is a Patch for it...for WLS8 ClientGen task...I dont remember the Patch Number Exactly.
    Just For testing:
    Just Use WLS9.x ClientGen task On the Same WSDL
    <taskdef name="clientgen" classname="weblogic.wsee.tools.anttasks.ClientGenTask" />
    I am sure you will not see this issue... because the issue is there only with WLS8 Clientgen...
    Thanks
    Jay SenSharma
    http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)
    Edited by: Jay SenSharma on Jan 8, 2010 4:32 PM
    Edited by: Jay SenSharma on Jan 8, 2010 4:34 PM

  • How the client stub is generated from the wsdl file ?

    I want to know how the client stub is generated from the wsdl file ?
    how the client accesses the methods in the wsdl fie ?
    thanks alot .

    there are several ways to generate the stubs from a wsdl.
    if you're using jax-ws, there is a netbeans tutorial creating web services. you found this on http://www.netbeans.org/kb/trails/web.html.
    if you're using axis as your framework, i think this would be a nice introduction of it. link : http://www.eli.sdsu.edu/courses/spring03/cs683/notes/AXIS/AXIS.html#Heading4

  • Generate Client Proxy from a RPC-Style encoded WSDL

    Hi Experts,
    I was just trying to consume a RPC-Style encoded WSDL,
    but the creation of the client proxy failed with the following error message:
    Exception occurred in library handler     
    Incorrect value: Unknown Namespace http://schemas.xmlsoap.org/soap/encoding/     
    Does anyone know, if it's possible to consume a RPC-Style encoded Web Service?
    Thanks in advance!

    Hi Sandeep,
    Could you try invoking clientgen [1] directly to see if this properly
    consumes your WSDL?
    Thanks,
    Bruce
    [1]
    http://e-docs.bea.com/wls/docs81/webserv/anttasks.html#1080160
    Sandeep wrote:
    >
    Hi,
    I am using Weblogic 8.1 SP1. I created a webservice which takes a XMLBean object
    as parameter and returns another XMLBean object. The web service works fine when
    tested using the workshop's test browser but when i am trying to generate a client
    proxy trough the workshop's test browser, it displays this warning:
    Failed to generate client proxy from WSDL definition for this service
    and does not generate the proxy.
    I'll appreciate any thoughts on this.
    Thanks
    Sandeep

  • Failed to generate client proxy from WSDL definition for this service

    Hi,
    I am using Weblogic 8.1 SP1. I created a webservice which takes a XMLBean object
    as parameter and returns another XMLBean object. The web service works fine when
    tested using the workshop's test browser but when i am trying to generate a client
    proxy trough the workshop's test browser, it displays this warning:
    Failed to generate client proxy from WSDL definition for this service
    and does not generate the proxy.
    I'll appreciate any thoughts on this.
    Thanks
    Sandeep

    Hi Sandeep,
    Could you try invoking clientgen [1] directly to see if this properly
    consumes your WSDL?
    Thanks,
    Bruce
    [1]
    http://e-docs.bea.com/wls/docs81/webserv/anttasks.html#1080160
    Sandeep wrote:
    >
    Hi,
    I am using Weblogic 8.1 SP1. I created a webservice which takes a XMLBean object
    as parameter and returns another XMLBean object. The web service works fine when
    tested using the workshop's test browser but when i am trying to generate a client
    proxy trough the workshop's test browser, it displays this warning:
    Failed to generate client proxy from WSDL definition for this service
    and does not generate the proxy.
    I'll appreciate any thoughts on this.
    Thanks
    Sandeep

  • Providing Certificate while generating a SSL client from wcf

    Hello,
    I am trying to generate a client from a wcf service which has an https endpoint which requires a certificate for authentication, when a try to connect to a web service from flash builder4 by providing the wsdl URI it give me the following error:
    There was an error during service introspection.
    WSDLException: faultCode=OTHER_ERROR: Unable to resolve imported document at 'https://hassanraza-pc/Service/UserManagerService.svc?wsdl'.: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
    Can some body help me....
    I need to know that how can i tell the flash builder about the certificate or if there is ny other way ....
    Thanks in anticipation:

    Hi, i'm facing the same issue .

Maybe you are looking for