WSDL Eclispe VS WebSphere Client Generation

Hi All,
I am facing issues while generating WSDL Clients on WebSphere plateform.
After generating the clients I am not able to execute the UCM services.
While when i generate the WSDL Client from Eclispe, I can successfully execute UCM Services.
Any pointers, as to how can this be avoided.
regards,
sapan
Edited by: sapan on Mar 9, 2009 7:27 AM
Solved it on my own, problem in selection of jars, dont forget to add obectpoolimpl.jar in your class path.

Hi Sapan,
I am able to generate sample client using IBM WID 6.2.
I am generating it using axis and with Websphere libraries.
What kind of error do you get ? make sure that you do not include any axis libraries.
I hope this will help you

Similar Messages

  • WsCompile script failed during initial client generation

    Hi all,
    I have NetBeans IDE 6.5 and GlassFishV2 installed on my pc. I tried to add a new web service client from an existing WSDL url to my java project but I get this error during adding the web service: “WsCompile script failed during initial client generation.”
    Why do I get this error message?
    Can anybody help me please?
    Note: WSDL made by Weblogic 11g and I have Jax-RPC 1.6 installed.

    Have you tried [XML RPC|http://ws.apache.org/xmlrpc/index.html]

  • Impossible to save settings for CIM Client Generation (in Visual Admin)

    Hi to all!
    I have next problem: the error 'Failed to set permissions for domain' appears when 'Save' button is pressed in Visual Administrator tool in 'SLD Data Supplier -> CIM Client Generation Settings' tab.
    I have administrative rights in Visual Admninistrator.
    What I need to do to save my settings?
    It's needed for estabilish connection between the J2EE AS and SLD service.
    This step required for using RFC adaptive model in Web Dynpro applications (for access to R/3 & functional models calling).
    Help me to resolve this issue,
    Thanx!

    Hi,
    ensure that you have gone through the following steps
    1)Go to : http://<host>:<port>/sld
    login as administrator
    2)Click on administration and it will take you to SLD server
    3)choose Start server and when the server is up choose stop server
    4)Go to server settings and make the entries for object server(localhost) and the working directory
    5)Choose database persistance and enter the relevent info for the ABAP system and choose 'set'
    6)Start data supplier bridge.Start SLD server also .Then go for importing the CIM instances
    Hope this helps you.Please dont forget to give points if it really helps.
    Regards,
    Rohit

  • Visual Admin - SLD Data Supplier - CIM Client Generation Settings Failing

    I am in VA -> cluster -> server -. services -> SLD data Supplier -> CIM Client Generation Settings.
    I am trying to save and I get the following error - "Failed to set permissions for domains"  I am using administrator for the id so I can eliminate permissions as a cause.  If I click on CIMClient test, it comes back successful.
    Any ideas?

    Hi Jason,
    Looks like the permission issue.
    Create a role called "Lcr administrator" and assign permission
    "Lcr administrator", "LCR write access" and "LCR read access"
    Then assigm "LCR administrator" to "Administrator" User.
    After that try doing CIM client settings again.
    Regards
    Usha

  • CIM Client generation settings

    Hello!!
    Does anyone know what User parameter settings i need to specify in CIM Client Generation Settings in Visual Administrator? I need to specify JCO connections in the WD Content Administrator and wanted to define the association between the logical system names used in model declaration and the actual SAP system.
    Thanks,
    Siva.

    Hi Siva,
    We need to give permissions  in Visual Administrator. These permissions enable us to create JCO connections in SLD, Start SLD server etc.
    In the above screen we have to give permission  to all the domain with “lcr” and “Webdynpro “
    host: localhost
    port:50000
    For user parameter settings give the administrator username and password for WAS server
    hope this helps you
    Regards
    Rohit

  • Problem in client generation from wsdl file

    Hi i am trying to generate client from a wsdl file through apache cxf framework, but it throws WSDLRefValidator error.
    Here is the error statment:
    Oct 11, 2012 11:51:33 AM org.apache.cxf.tools.validator.internal.WSDLRefValidator collectValidationPoints
    WARNING: WSDL document file:/D:/latestWS20120925/WebServiceTest26092012/WebContent/wsdl/PlmWebserviceImportGcas.wsdl does not define any services
    WSDLToJava Error:
    line 5 column 646 of file:/D:/latestWS20120925/WebServiceTest26092012/WebContent/wsdl/PlmWebserviceImportGcas.wsdl: cvc-complex-type.2.4.a: Invalid content was found starting with element 'WL5G3N0:definitions'. One of '{"http://www.w3.org/2001/XMLSchema":include, "http://www.w3.org/2001/XMLSchema":import, "http://www.w3.org/2001/XMLSchema":redefine, "http://www.w3.org/2001/XMLSchema":annotation, "http://www.w3.org/2001/XMLSchema":simpleType, "http://www.w3.org/2001/XMLSchema":complexType, "http://www.w3.org/2001/XMLSchema":group, "http://www.w3.org/2001/XMLSchema":attributeGroup, "http://www.w3.org/2001/XMLSchema":element, "http://www.w3.org/2001/XMLSchema":attribute, "http://www.w3.org/2001/XMLSchema":notation}' is expected.
    org.apache.cxf.tools.common.ToolException:
    line 5 column 646 of file:/D:/latestWS20120925/WebServiceTest26092012/WebContent/wsdl/PlmWebserviceImportGcas.wsdl: cvc-complex-type.2.4.a: Invalid content was found starting with element 'WL5G3N0:definitions'. One of '{"http://www.w3.org/2001/XMLSchema":include, "http://www.w3.org/2001/XMLSchema":import, "http://www.w3.org/2001/XMLSchema":redefine, "http://www.w3.org/2001/XMLSchema":annotation, "http://www.w3.org/2001/XMLSchema":simpleType, "http://www.w3.org/2001/XMLSchema":complexType, "http://www.w3.org/2001/XMLSchema":group, "http://www.w3.org/2001/XMLSchema":attributeGroup, "http://www.w3.org/2001/XMLSchema":element, "http://www.w3.org/2001/XMLSchema":attribute, "http://www.w3.org/2001/XMLSchema":notation}' is expected.
         at org.apache.cxf.tools.validator.internal.SchemaValidator.validate(SchemaValidator.java:203)
         at org.apache.cxf.tools.validator.internal.SchemaValidator.validate(SchemaValidator.java:119)
         at org.apache.cxf.tools.validator.internal.SchemaValidator.isValid(SchemaValidator.java:103)
         at org.apache.cxf.tools.validator.internal.WSDL11Validator.isValid(WSDL11Validator.java:157)
         at org.apache.cxf.tools.wsdlto.frontend.jaxws.wsdl11.JAXWSDefinitionBuilder.validate(JAXWSDefinitionBuilder.java:204)
         at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.processWsdl(WSDLToJavaContainer.java:182)
         at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:142)
         at org.apache.cxf.tools.wsdlto.WSDLToJavaContainer.execute(WSDLToJavaContainer.java:300)
    The excerpt from wsdl file is provided below:
    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" name="PlmWebserviceImportGcas.wsdl" targetNamespace="D:/webservice">
    <wsdl:types>
    <xsd:schema xmlns="http://www.pg.com/css/webservice" xmlns:xsd="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" targetNamespace="http://www.pg.com/css/webservice">
    *<WL5G3N0:definitions xmlns="" xmlns:WL5G3N0="http://schemas.xmlsoap.org/wsdl/" xmlns:WL5G3N1="http://www.pg.com/Inputs/HubPollForTSStatusInput" xmlns:WL5G3N2="http://www.pg.com/Outputs/HubPollForTSStatusOutput" xmlns:WL5G3N3="http:/www.pg.com/productNet/HubSubmitForumlatoCSSInput" xmlns:WL5G3N4="http:/www.pg.com/productNet/HubSubmitForumlatoCSSOutput" xmlns:WL5G3N5="http://www.pg.com/Inputs/HubDeleteTSRequestInput" xmlns:WL5G3N6="http://www.pg.com/Outputs/HubDeleteTSRequestOutput" xmlns:WL5G3N7="http://www.pg.com/WS/FormulaHubWS" xmlns:WL5G3N8="http://schemas.xmlsoap.org/wsdl/soap/" targetNamespace="http://www.pg.com/WS/FormulaHubWS">*
    <WL5G3N0:types>
    <xsd:schema xmlns="http:/www.pg.com/productNet/HubSubmitForumlatoCSSOutput" xmlns:CSS_SubmitFormulaOutput.xsd="http://pg.com/Inputs/CSS_SubmitFormulaOutput" xmlns:ns2="http://www.pg.com/Inputs/HubPollForTSStatusInput" xmlns:ns3="http://www.pg.com/Outputs/HubPollForTSStatusOutput" xmlns:ns4="http:/www.pg.com/productNet/HubSubmitForumlatoCSSInput" xmlns:ns5="http:/www.pg.com/productNet/HubSubmitForumlatoCSSOutput" xmlns:ns6="http://www.pg.com/Inputs/HubDeleteTSRequestInput" xmlns:ns7="http://www.pg.com/Outputs/HubDeleteTSRequestOutput" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://www.pg.com/WS/FormulaHubWS" attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http:/www.pg.com/productNet/HubSubmitForumlatoCSSOutput">
                                  <xsd:import namespace="http://pg.com/Inputs/CSS_SubmitFormulaOutput"/>
                                  <xsd:element name="SubmitFormulatoCSSOutput">
                                       <xsd:complexType>
                                            <xsd:sequence>
                                                 <xsd:element ref="CSS_SubmitFormulaOutput.xsd:SubmitFormulatoCSS_Output"/>
    It seems to be problem with tag WL5G3NO declaration.
    Can anyone suggest how to rectify this?
    Thanks

    Have you tried pulling the schema out of the wsdl and putting it in a xsd file and see if it validates?
    Otherwise, have you tried removing the xmlns:"" from <WL5G3N0:definitions xmlns:"".
    Edited by: C.Stodden on Oct 11, 2012 8:52 AM

  • Web Service Client Generation on 7.10 SP3 - No WSDL URL is specified....

    We have a mysterious problem here.
    In out ABAP system we had a WebService created. With "New - Web Service Client" we created a web service client on the java side for that one and we were able to invoke it.
    We had to recreate this Web service due to wrong naming conventions. And now the problem starts.
    In the Main service class we had before something generated by NWDS:
    private static java.net.URL SERVICES_SERVICE_WSDL_LOCATION = null;
    static {
        java.net.URL url = null;
        try {
              java.net.URL tmpUrl = Thread.currentThread().getContextClassLoader().getResource("wsdl/com/sap/document/sap/soap/functions/mc_style/sap/bc/srt/wsdl/bndg_001279D063121DECA58AC5F7200DC55D/wsdl11/allinone/ws_policy/document/rootwsdl_SERVICES.wsdl");
              url = new java.net.URL(tmpUrl.getProtocol(), tmpUrl.getHost(), tmpUrl.getPort(), tmpUrl.getFile());
        } catch (java.net.MalformedURLException e) {
          e.printStackTrace();
        SERVICES_SERVICE_WSDL_LOCATION = url;
    After the new creation with the new Web Service this static initializer is gone an we see:
    private final static java.net.URL SERVICE_WSDL_LOCATION = null;
    This code is ridiculous, to make something static final and set it to Null. And as expected at runtime it results in WebServioceException telling us:
    No WSDL URL is specified for service [class com.sap.document.sap.soap.functions.mc_style.Service] on service creation.
    Anyone knows what is going wrong here??
    Best regards,
    Frank

    Same problem here.
    From Netweaver dev studio, I'm generating a deployable proxy for a Session Bean that is supposed to access a webservice but I keep getting the exception:
    "Caused by: javax.xml.ws.WebServiceException: No WSDL URL is specified for service [class eu.socrades.sap.ServiceMonitorBeanTESTService] on service creation.
    at com.sap.engine.services.webservices.espbase.client.jaxws.core.SAPServiceDelegate.<init>(SAPServiceDelegate.java:108)
    at com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider.createDelegate(CTSProvider.java:170)
    at com.sap.engine.services.webservices.espbase.client.jaxws.cts.CTSProvider.createServiceDelegate(CTSProvider.java:151)
    at javax.xml.ws.Service.<init>(Service.java:57)
    at eu.socrades.sap.ServiceMonitorBeanTESTService.<init>(ServiceMonitorBeanTESTService.java:14)"
    I'm injecting the reference to the service with:
    @WebServiceRef(wsdlLocation = "rootwsdl_ServiceMonitorBeanTESTService.wsdl")
    private ServiceMonitorBeanTESTService service;
    I tried changing the location to a URL (where the wsdl can be downloaded from) or to "META-INF/wsdl/eu/socrades/sap/rootwsdl_ServiceMonitorBeanTESTService/rootwsdl_ServiceMonitorBeanTESTService.wsdl" but that did not help.
    Any clue?
    Thanks a lot,
    Dom

  • Java client generation from BPEL WSDL fails?

    Hi -
    I have developed asynchronous BPEL composite project and used input xsd as required.Deployed the same on em and took wsdl url.
    In OSB project this WSDL from abve step is used as input for proxy service.Exported WSDL from this proxy and trying to create java client out of it.
    In eclipse or OEPE if i load above wsdl and provide >generate webservice java client,it through exception saying 'root tag'(of our xsd) not define?
    Can we generate Java client out of WSDL deployed and available on BPEL em?If so how?
    Please assist..
    Edited by: Anitha R on Jan 23, 2011 2:36 AM

    This is fixed.We were able to generate the cient,namespace required for input message found missing.After udation it worked.

  • Stub/Client Generation of WSDL for Windows Communication Foundation Service

    Hii,
    I am building a client for the WCF service using Soap1.2 and ws-security. I have tried building a stub for the service using JDeveloper 10 g and also tried to validate the wsdl using XML spy. Both are giving errors. I wanna know how could i genrate the stub for the service and also Validate WSDL? I know i might have to modify the WSDL, but dont know what changes must be required? And Also which std i must adhere?
    Here is the WSDL
    <?xml version="1.0" encoding="utf-8"?>
    <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
                      xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
                      xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
                      xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
                      xmlns:wsap10="http://www.w3.org/2005/08/addressing"
                      xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
                      xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy"
                      xmlns:i0="http://Corona.Services.UserMgmt.UserMgmtSrv"
                      xmlns:wsap="http://schemas.xmlsoap.org/ws/2004/09/policy/addressing"
                      xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                      xmlns:msc="http://schemas.microsoft.com/ws/2005/12/wsdl/contract"
                      xmlns:tns="http://tempuri.org/"
                      xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
                      xmlns:wsx="http://schemas.xmlsoap.org/ws/2004/09/mex"
                      xmlns:wsa10="http://www.w3.org/2005/08/addressing"
                      targetNamespace="http://tempuri.org/" name="UserMgmtSrv">
      <wsdl:import namespace="http://Corona.Services.UserMgmt.UserMgmtSrv"
                   location="http://debugger/Corona.Services/Corona.Services.svc?wsdl"/>
      <wsdl:types/>
      <wsdl:binding name="WSHttpBinding_UserMgmtSrv" type="i0:UserMgmtSrv">
        <wsp:PolicyReference URI="#WSHttpBinding_UserMgmtSrv_policy"/>
        <soap12:binding transport="http://schemas.xmlsoap.org/soap/http"/>
        <wsdl:operation name="Authenticate">
          <wsdl:input>
            <soap12:body use="literal"/>
          </wsdl:input>
          <wsdl:output>
            <soap12:body use="literal"/>
          </wsdl:output>
          <wsdl:fault name="ArgumentExceptionFault">
            <soap12:fault name="ArgumentExceptionFault"
                          namespace="http://Corona.Services.UserMgmt.UserMgmtSrv.FaultException"/>
          </wsdl:fault>
        </wsdl:operation>
        <wsdl:operation name="SaveHealthProfileWrapper">
          <wsdl:input>
            <soap12:body use="literal"/>
          </wsdl:input>
          <wsdl:output>
            <soap12:body use="literal"/>
          </wsdl:output>
        </wsdl:operation>
      </wsdl:binding>
      <wsdl:service name="UserMgmtSrv">
        <wsdl:port name="WSHttpBinding_UserMgmtSrv"
                   binding="tns:WSHttpBinding_UserMgmtSrv">
          <soap12:address location="https://debugger/Corona.Services/Corona.Services.svc"/>
          <wsa10:EndpointReference>
            <wsa10:Address>https://debugger/Corona.Services/Corona.Services.svc</wsa10:Address>
          </wsa10:EndpointReference>
        </wsdl:port>
      </wsdl:service>
      <wsp:Policy wsu:Id="WSHttpBinding_UserMgmtSrv_policy">
        <wsp:ExactlyOne>
          <wsp:All>
            <wspe:Utf816FFFECharacterEncoding xmlns:wspe="http://schemas.xmlsoap.org/ws/2004/09/policy/encoding"/>
            <sp:TransportBinding xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
              <wsp:Policy>
                <sp:TransportToken>
                  <wsp:Policy>
                    <sp:HttpsToken RequireClientCertificate="false"/>
                  </wsp:Policy>
                </sp:TransportToken>
                <sp:AlgorithmSuite>
                  <wsp:Policy>
                    <sp:Basic128/>
                  </wsp:Policy>
                </sp:AlgorithmSuite>
                <sp:Layout>
                  <wsp:Policy>
                    <sp:Strict/>
                  </wsp:Policy>
                </sp:Layout>
                <sp:IncludeTimestamp/>
              </wsp:Policy>
            </sp:TransportBinding>
            <sp:EndorsingSupportingTokens xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
              <wsp:Policy>
                <sp:SecureConversationToken sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient">
                  <wsp:Policy>
                    <mssp:RequireCancel wsp:Optional="true"
                                        xmlns:mssp="http://schemas.microsoft.com/ws/2005/07/securitypolicy"/>
                    <sp:BootstrapPolicy>
                      <wsp:Policy>
                        <sp:TransportBinding>
                          <wsp:Policy>
                            <sp:TransportToken>
                              <wsp:Policy>
                                <sp:HttpsToken RequireClientCertificate="false"/>
                              </wsp:Policy>
                            </sp:TransportToken>
                            <sp:AlgorithmSuite>
                              <wsp:Policy>
                                <sp:Basic128/>
                              </wsp:Policy>
                            </sp:AlgorithmSuite>
                            <sp:Layout>
                              <wsp:Policy>
                                <sp:Strict/>
                              </wsp:Policy>
                            </sp:Layout>
                            <sp:IncludeTimestamp/>
                          </wsp:Policy>
                        </sp:TransportBinding>
                        <sp:EndorsingSupportingTokens>
                          <wsp:Policy>
                            <sp:SpnegoContextToken sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient">
                              <wsp:Policy>
                                <mssp:RequireCancel wsp:Optional="true"
                                                    xmlns:mssp="http://schemas.microsoft.com/ws/2005/07/securitypolicy"/>
                              </wsp:Policy>
                            </sp:SpnegoContextToken>
                          </wsp:Policy>
                        </sp:EndorsingSupportingTokens>
                        <sp:Trust10>
                          <wsp:Policy>
                            <sp:MustSupportIssuedTokens/>
                            <sp:RequireClientEntropy/>
                            <sp:RequireServerEntropy/>
                          </wsp:Policy>
                        </sp:Trust10>
                      </wsp:Policy>
                    </sp:BootstrapPolicy>
                  </wsp:Policy>
                </sp:SecureConversationToken>
              </wsp:Policy>
            </sp:EndorsingSupportingTokens>
            <sp:Trust10 xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
              <wsp:Policy>
                <sp:MustSupportIssuedTokens/>
                <sp:RequireClientEntropy/>
                <sp:RequireServerEntropy/>
              </wsp:Policy>
            </sp:Trust10>
            <wsap10:UsingAddressing/>
          </wsp:All>
        </wsp:ExactlyOne>
      </wsp:Policy>
      <wsp:UsingPolicy/>
    </wsdl:definitions>

    I had the problem with JDev (9.0.4) when trying to generate server side classes from a homemade wsdl which took a complex type as a parameter. The only thing I got from JDeveloper was a class receiving an Element. Which pretty much means you have to do the work yourself.
    Quite disappointing....!
    I see to possibilities:
    1) If you are stuck with 9.0.4 you will have to parse to and from xml yourself. For this you can use jax-b which is a Sun API used to create classes for a given XML Schema to parse and validate XML. You have some work creating the classes, but it runs very fast when you have generated the classes.
    2) You use the topdown approach described on OTN. http://www.oracle.com/technology/sample_code/tech/java/codesnippet/webservices/doc-lit/index.html
    I think this is the example for OC4J (9.0.4). There is a new and improved version of the tool (wsa.jar) with the new OC4J (10.1.3)
    Have fun......and I am sure that Oracle quite soon will deliver the functionality directly from JDev....:-)
    /Peter

  • Web service proxy client generation fails

    Hello,
    i want to generate a webservice proxy client of a web service. For the access to the wsdl file of this web service, basic authentication is required. How can i use the proxy generation tool with username and password? The wsa.jar -genProxy doesn't work because i dont know how i can submit username and password. Is it possible to integrate username and password anywhere?? Is there an other way to generate a webservice proxy client? Please help me :(
    Thanks a lot from Berlin!
    Tom

    Hello,
    i want to generate a webservice proxy client of a web service. For the access to the wsdl file of this web service, basic authentication is required. How can i use the proxy generation tool with username and password? The wsa.jar -genProxy doesn't work because i dont know how i can submit username and password. Is it possible to integrate username and password anywhere?? Is there an other way to generate a webservice proxy client? Please help me :(
    Thanks a lot from Berlin!
    Tom

  • JAXRPC ws-client generation failure with WL10.3

    Hi all.
    My deep apologies for crossposting; this question was posted first to "WebLogic Server - Upgrade" forum and just later I found this webservices related topic.
    I'm copying it as it for for the sake of convenience.
    I'm facing a problem to generate web-service client with WL-10.3, while WL-9.2 works pretty fine with this WSDL.
    My ANT task is:
    <clientgen
    type="JAXRPC"
    wsdl="${WSDL}"
    destDir="${DESTDIR}"/>
    In case type is set to JAXWS, generation succeeds. However, if I set it to JAXRPC (I need to enable multirefs to support closed graphs), the generation fails with exception:
    weblogic.wsee.tools.WsBuildException: weblogic.descriptor.DescriptorException: Failed to marshal: weblogic.j2ee.descriptor.JavaWsdlMappingBeanImpl
    at weblogic.wsee.tools.anttasks.ClientGenFacadeTask.execute(ClientGenFacadeTask.java:235)
    at weblogic.wsee.tools.anttasks.ClientGenTask.execute(ClientGenTask.java:358)
    Caused by: java.io.IOException
    at weblogic.descriptor.internal.MarshallerFactory.<init>(MarshallerFactory.java:50)
    at weblogic.descriptor.BasicDescriptorManager.getMarshallerFactory(BasicDescriptorManager.java:137)
    Caused by: com.bea.xml.XmlException: unable to load type library from classloader org.apache.tools.ant.AntClassLoader@104c575
    at com.bea.staxb.runtime.internal.BindingContextFactoryImpl.createBindingContext(BindingContextFactoryImpl.java:50)
    at weblogic.descriptor.internal.MarshallerFactory.<init>(MarshallerFactory.java:48)
    Are there any known limitations/issues regarding JAXRPC support for WL-10.3?
    Is there any workaround for this problem?
    Greatly appreciating any inputs
    Sincerely
    Jabb

    Updates.
    Meanwhile I found that the mentioned failure is caused due to inner calls to ClassLoader.getResources() searches for "META-INF/binding-file.ser" and "META-INF/binding-mapping-file.ser" calls which returns empty results. However these files were succesfully created in directory pointed by destDir attribute. I added the destDir dir to taks's classpath:
    <clientgen
    type="JAXRPC"
    wsdl="${WSDL}"
    destDir="${DESTDIR}">
    <classpath>
         <pathelement location="${DESTDIR}"/>
    </classpath>
    </clientgen>
    and this faulire was gone, but new appeared:
    weblogic.wsee.tools.WsBuildException: weblogic.descriptor.DescriptorException: Failed to marshal: weblogic.j2ee.descriptor.JavaWsdlMappingBeanImpl
         at weblogic.wsee.tools.anttasks.ClientGenFacadeTask.execute(ClientGenFacadeTask.java:235)
    Caused by: com.bea.xml.XmlException: failed to find root element corresponding to weblogic.j2ee.descriptor.JavaWsdlMappingBeanImpl
         at com.bea.staxb.runtime.internal.MarshallerImpl.lookupRootElementName(MarshallerImpl.java:70)
         at com.bea.staxb.runtime.internal.MarshallerImpl.marshal(MarshallerImpl.java:139)
         at com.bea.staxb.runtime.internal.MarshallerImpl.marshal(MarshallerImpl.java:191)
         at weblogic.descriptor.BasicDescriptorManager.writeDescriptorBeanAsXML(BasicDescriptorManager.java:503)

  • Axis2  1.4 client Generation for EJB3 service - RPC Encoded

    I am trying to create a Webservice client in eclipse and i am using AXIS2(1.4) environment but when i try wsdl to java, i get the following exception.
    Exception occurred while code generation for WSDL : org.apache.axis2.AxisFault: Encoded use is not supported
    My WSDL has the following encoding. I couldn't understand why is this not supported. As i have used this encoding because i was getting the Circular reference serializing problem.
    @SOAPBinding(style = SOAPBinding.Style.RPC, use= SOAPBinding.Use.ENCODED)
    code:
    <input>
    <soap:body use="encoded" namespace="http://service.ejb/" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
    </input>
    <output>
    <soap:body use="encoded" namespace="http://service.ejb/" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" parts="return"/>
    </output>
    Any pointers are appreciated.
    Thanks,
    Rahul

    I am trying to create a Webservice client in eclipse and i am using AXIS2(1.4) environment but when i try wsdl to java, i get the following exception.
    Exception occurred while code generation for WSDL : org.apache.axis2.AxisFault: Encoded use is not supported
    My WSDL has the following encoding. I couldn't understand why is this not supported. As i have used this encoding because i was getting the Circular reference serializing problem.
    @SOAPBinding(style = SOAPBinding.Style.RPC, use= SOAPBinding.Use.ENCODED)
    code:
    <input>
    <soap:body use="encoded" namespace="http://service.ejb/" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
    </input>
    <output>
    <soap:body use="encoded" namespace="http://service.ejb/" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" parts="return"/>
    </output>
    Any pointers are appreciated.
    Thanks,
    Rahul

  • Get the WSDL-File used for proxy generation

    Hello everybody!
    I created a Web Service Proxy:
    SE80 -> Select Package -> Enterprise Services -> Client Proxies -> New -> WSDL Source: Local File.
    Everything worked out fine. I was able to create that Proxy.
    Now I would like to look at the WSDL-File that has been used:
    If I take a look at that Proxy by SE80 -> Select Package -> Enterprise Services -> Client Proxies -> [Select Proxy] -> Display in new Window -> Goto: The Menue Entry "Display WSDL Document" unfortunately is disabled.
    I have not configured the integration builder.
    Is there a possibility to get the WSDL-file that has been used for the generated proxy? Does anybody know, if the WSDL-file, that has been used for the proxy generation is archived somewhere in the system?
    Thanks,
    Andreas

    Hello,
    Thanks for your reply.
    I am using SAP ECC 6.0:
    SAP_BASIS     700     0010     SAPKB70010     SAP Basis Component
    SAP_ABA     700     0010     SAPKA70010     Cross-Application Component
    Unfortunately the tab "Proxy Generation" at Utilities -> Settings is not available with my release.
    Any other idea?
    Greetings,
    Andreas

  • Axis2 and wsdl- Exception thrown when client attempting server connection

    Hi all,
    I am trying at the moment to develop an Axis2 server, and test it with a client.
    The server is to provide a soap wsdl service, returning an object request.
    I have generated server code and client code using axis2's wsdl2java tool, and all seemed fine.
    The server I created using this generated code seems to work, so far as i can tell, as I can connect to it through a browser.
    For example, using the browser I can connect to it via:
    http://localhost:8888/services/PersonInfo
    and it gives me a page showing 'Deployed Services', listing the operations available.
    but the funny thing is here that it seems to auto-direct me to another url: http://localhost:8888/axis2/services/ which I have not specified.
    For the server I am using the axis2 supplied SimpleHTTPServer. Here is the complete code excluding the actual generated code:
    public class EmbeddedAxis2Server {
        public static void main(String[] args) throws Exception {
            ConfigurationContext context = ConfigurationContextFactory.
            createConfigurationContextFromFileSystem(null, null);
            AxisService service =
            AxisService.createService(caps.integration.rhos.dk.schema.astraiaservice._2008._04._15.PersonInfo.class.getName(), context.getAxisConfiguration());
            context.getAxisConfiguration().addService(service);
            SimpleHTTPServer server = new SimpleHTTPServer(context, 8888);
            server.start();
    }I can even call the published operation using the browser, via the url:
    http://localhost:8888/axis2/services/PersonInfo/getPersonInfo
    and pass in arguments using the usual form variables syntax.
    HOWEVER!! My problem is (and maybe it is related to the url redirect strangeness I mentioned above, or maybe not), that my coded client is not able to connect.
    I generated the client stubs also using wsdl2java, and call the functions... but I get this show stopping exception:
    org.apache.axis2.AxisFault: The service cannot be found for the endpoint reference (EPR) 127.0.0.1/services/PersonInfo
         at org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:486)
         at org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:343)
         at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389)
         at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
         at org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
         at caps.integration.rhos.dk.schema.astraiaservice._2008._04._15.PersonInfoStub.getPersonInfo(PersonInfoStub.java:142)
         at com.astraia.axisclient.Client.getPersonInfo(Client.java:44)
         at com.astraia.axisclient.Client.main(Client.java:23)Here is the client code (excluding generated stub)
        public static void getPersonInfo(){
            try
                 ConfigurationContext context = ConfigurationContextFactory.createConfigurationContextFromFileSystem(null, null);
                 PersonInfoStub stub =new PersonInfoStub(context);
                GetPersonInfoIn req =new GetPersonInfoIn();
                req.setCivilRegistrationIdentifier("CIV123");
                req.setHospitalCode("HOS123");
                req.setRequestId("123");
                req.setUserName("sean");
                GetPersonInfoOut res = stub.getPersonInfo(req);
                System.out.println(res.toString());
            } catch(Exception e){     e.printStackTrace();       System.out.println("\n\n\n");      }
        }If anyone has any idea of what this problem is about, I would love to hear about it!
    Kind Regards,
    svaens
    Edited by: svaens on Apr 28, 2008 2:11 AM

    Hi, I have an update!!!
    Another aspect of my problem (which I had forgotten to mention) was a mysterious difference in the original wsdl file, and the one that was generated by my SImpleHTTPServer when my browser contact it, and requested the wsdl. That is, when I use the url in my firefox browser
    [http://localhost:8888/axis2/services/PersonInfo?wsdl|http://localhost:8888/axis2/services/PersonInfo?wsdl]
    the wsdl that was returned to the browser was different in several ways to the original wsdl that I generated my server side java code from using the axis2-1.3 wsdl2java.sh script.
    I had noticed this, and decided to create a client using this new and strangely different wsdl, and see if this provides different results.
    It worked!!! After creating my stub java code with the new wsdl file, and the wsdl2java tool, and modifying my custom java code to match the different stub generated, the client was able to connect to the server, and return me a serialized object.
    Does this give you any clues as to what may be the real problem?
    Differences in the wsdl include:
    1. the targetNamespace attribute listed in the wsdl:definitions tag shows the namespace backwards!!
    2. The new generated wsdl file has two extra element types,
    GetPersonInfo, and GetPersonInfoResponse, + GetPersonInfoIn , GetPersonInfoOut
    while the original only game me GetPersonInfoOut & GetPersonInfoIn.
    The client code I had to change now looks like this:
    try
                ConfigurationContext context = ConfigurationContextFactory.
                createDefaultConfigurationContext();
            PersonInfoStub stub =  new PersonInfoStub(context);
                GetPersonInfo reqs =   new GetPersonInfo();
                GetPersonInfoIn req = new GetPersonInfoIn();
                reqs.setGetPersonInfoIn(req);
                req.setCivilRegistrationIdentifier("CIV123");
                req.setHospitalCode("HOS123");
                req.setRequestId("123");
                req.setUserName("sean");
                GetPersonInfoResponse res = stub.getPersonInfo(reqs);
                GetPersonInfoOut resultObj = res.get_return();
                            OMFactory fac = OMAbstractFactory.getOMFactory();
                            OMElement xml = resultObj.getOMElement(GetPersonInfoResponse.MY_QNAME, fac);
                            XMLStreamWriter writer = XMLOutputFactory.newInstance().createXMLStreamWriter(System.out);
                            writeOMElement(xml, writer);
            } catch(Exception e){
                e.printStackTrace();
                System.out.println("\n\n\n");
            }

  • Integrated Windows Authentication with a WebSphere Cliente

    Hi all,
    I need to write a web service client that connects to a .NET Web Service that is configured to use Integrated Windows Authentication (NTLM).
    I'm using the IBM WebSphere Runtime environment for the client and using the web service client wizard in the RSD 6.0.1.
    When I try to call a method in the .NET web service, I get the error shown below. If I configure the .NET web service to permit Anonymous Access, my client works fine.
    Does anybody know if the WebSphere web services engine supports Integrated Windows Authentication? If so, how can I configure my cliente to pass my credentials? Do people use this type of authentication if the web service will be called by non Windows clientes or is it better to use Basic Authentication with HTTPS or digital certificates?
    I've read that Apache Axis can be configured to use integrated windows authentication (http://people.etango.com/~markm/archives/2005/11/21/using_apache_axis_with_integrated_windows_security.html) by using a different HTTP transport class (CommonsHTTPSender).
    Thanks in advance!
    Craig
    [14/06/06 10:06:56:805 GMT-03:00] 00000031 enterprise I WSWS3243I: Info: Mapping Exception to WebServicesFault.
    [14/06/06 10:06:56:821 GMT-03:00] 00000031 enterprise I TRAS0014I: The following exception was logged WebServicesFault
    faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.generalException
    faultString: java.lang.StringIndexOutOfBoundsException
    faultActor: null
    faultDetail:
    java.lang.StringIndexOutOfBoundsException
         at com.ibm.ws.webservices.engine.WebServicesFault.makeFault(WebServicesFault.java:179)
         at com.ibm.ws.webservices.engine.transport.http.HTTPSender.invoke(HTTPSender.java:490)
         at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:218)
         at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:218)
         at com.ibm.ws.webservices.engine.WebServicesEngine.invoke(WebServicesEngine.java:274)
         at com.ibm.ws.webservices.engine.client.Connection.invokeEngine

    Here's a project ( [http://spnego.sourceforge.net/protected_soap_service.html|http://spnego.sourceforge.net/protected_soap_service.html] ) that shows how to write a soap client that can connect to a soap web service with integrated windows authentication turned on.

Maybe you are looking for