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

Similar Messages

  • Error while generating java client code from wsdl file

    I am trying to generate a java client code from WSDL file um_workflowSaveCreateProfile.wsdl which includes um_workflowSaveCreateProfile_interface.wsdl file, so I am keeping both the files in the same folder and trying to generate the client code but it is showing me the below error highlighted .
    um_workflowSaveCreateProfile.wsdl
    <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xsd="E:/DIPPWF/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:oblix="http://www.oblix.com/" xmlns:obinterface="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile_interface" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile" targetNamespace="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile">
         <import namespace="D:/DIPP/WSDL/um_workflowSaveCreateProfile_interface" location="um_workflowSaveCreateProfile_interface.wsdl"/>
         <service name="OblixIDXML_um_workflowSaveCreateProfile_Service">
              <port name="OblixIDXML_um_workflowSaveCreateProfile_Port" binding="obinterface:OblixIDXML_um_workflowSaveCreateProfile_Binding">
                   <soap:address location="http://localhost:7777/identity/oblix/apps/userservcenter/bin/userservcenter.cgi"/>
              </port>
         </service>
    </definitions>
    um_workflowSaveCreateProfile_interface.wsdl
    <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:oblix="http://www.oblix.com/" xmlns:oblixxmllocalschema="http://www.oblix.com/OblixXMLLocalSchema" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile_interface" targetNamespace="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile_interface">
         <types>
              <xsd:schema targetNamespace="http://www.oblix.com/" elementFormDefault="qualified"
                   xmlns="http://www.oblix.com/"
                   xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                        <xsd:include schemaLocation="../XMLSchema/common_parameters.xsd" />
                        <xsd:include schemaLocation="../XMLSchema/common_authentication.xsd" />
                        <xsd:include schemaLocation="../XMLSchema/workflowSaveCreateProfile.xsd" />
              </xsd:schema>
              <xsd:schema targetNamespace="http://www.oblix.com/OblixXMLLocalSchema" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
                   <xsd:element name="request">
                        <xsd:complexType>
                             <xsd:sequence>
                                  <xsd:element name="params">
                                       <xsd:complexType>
                                            <xsd:sequence>
                                                 <xsd:element ref="oblix:ObWorkflowName"/>
                                                 <xsd:element ref="oblix:ObDomainName"/>
                                                 <xsd:element ref="oblix:ObWfComment" minOccurs="0"/>
                                                 <xsd:element ref="oblix:noOfFields"/>
                                                 <xsd:element ref="oblix:AttributeParams"/>
                                            </xsd:sequence>
                                       </xsd:complexType>
                                  </xsd:element>
                             </xsd:sequence>
                             <xsd:attribute name="version" type="xsd:string" use="optional"/>
                             <xsd:attribute name="application" type="xsd:string" use="required" />
                             <xsd:attribute name="function" type="xsd:string" use="required" />
                             <xsd:attribute name="mode" type="xsd:string" use="optional"/>
                        </xsd:complexType>
                   </xsd:element>
              </xsd:schema>
         </types>
         <message name="OblixIDXMLInput">
              <part name="authentication" element="oblix:authentication"/>
              <part name="request" element="oblixxmllocalschema:request"/>
         </message>
         <message name="OblixIDXMLOutput">
              <part name="body" element="oblix:Oblix"/>
         </message>
         <portType name="OblixIDXMLPortType">
              <operation name="OblixIDXML_um_workflowSaveCreateProfile">
                   <input message="tns:OblixIDXMLInput"/>
                   <output message="tns:OblixIDXMLOutput"/>
              </operation>
         </portType>
         <binding name="OblixIDXML_um_workflowSaveCreateProfile_Binding" type="tns:OblixIDXMLPortType">
              <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
              <operation name="OblixIDXML_um_workflowSaveCreateProfile">
                   <soap:operation soapAction="http://www.oblix.com/"/>
                   <input>
                        <soap:body use="literal"/>
                   </input>
                   <output>
                        <soap:body use="literal"/>
                   </output>
              </operation>
         </binding>
    </definitions>
    I am using WSDL2 Java for generating the client code .
    Please suggest where am I wrong .
    E:\axis2-1.4\bin>WSDL2Java -uri E:\DIPPWF\um_workflowSaveCreateProfile.wsdl -p R
    ND -d adb -s -o build\client--http-proxy-host 10.74.93.35 --http-proxy-port 80
    Using AXIS2_HOME: E:\axis2-1.4
    Using JAVA_HOME: C:\Program Files\Java\jdk1.6.0_02
    Retrieving document at 'E:\DIPPWF\um_workflowSaveCreateProfile.wsdl'.
    Retrieving document at 'um_workflowSaveCreateProfile_interface.wsdl', relative t
    o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile.wsdl'.
    Retrieving schema at 'E:/DIPPWF/XMLSchema/common_parameters.xsd', relative to 'f
    ile:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
    Retrieving schema at 'E:/DIPPWF/XMLSchema/common_authentication.xsd', relative t
    o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
    Retrieving schema at 'E:/DIPPWF/XMLSchema/workflowSaveCreateProfile.xsd', relati
    ve to 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
    Retrieving schema at 'navbar.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/workfl
    owSaveCreateProfile.xsd'.
    Retrieving schema at 'searchform.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/wo
    rkflowSaveCreateProfile.xsd'.
    Retrieving schema at 'component_basic.xsd', relative to 'file:/E:/DIPPWF/XMLSche
    ma/workflowSaveCreateProfile.xsd'.
    Retrieving schema at 'displaytype.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/c
    omponent_basic.xsd'.
    Retrieving schema at 'error.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/compone
    nt_basic.xsd'.
    Retrieving schema at 'component_workflowTicket.xsd', relative to 'file:/E:/DIPPW
    F/XMLSchema/workflowSaveCreateProfile.xsd'.
    Retrieving document at 'E:\DIPPWF\um_workflowSaveCreateProfile.wsdl'.
    Retrieving document at 'um_workflowSaveCreateProfile_interface.wsdl', relative t
    o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile.wsdl'.
    Retrieving schema at 'E:/DIPPWF/XMLSchema/common_parameters.xsd', relative to 'f
    ile:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
    Retrieving schema at 'E:/DIPPWF/XMLSchema/common_authentication.xsd', relative t
    o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
    Retrieving schema at 'E:/DIPPWF/XMLSchema/workflowSaveCreateProfile.xsd', relati
    ve to 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
    Retrieving schema at 'navbar.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/workfl
    owSaveCreateProfile.xsd'.
    Retrieving schema at 'searchform.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/wo
    rkflowSaveCreateProfile.xsd'.
    Retrieving schema at 'component_basic.xsd', relative to 'file:/E:/DIPPWF/XMLSche
    ma/workflowSaveCreateProfile.xsd'.
    Retrieving schema at 'displaytype.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/c
    omponent_basic.xsd'.
    Retrieving schema at 'error.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/compone
    nt_basic.xsd'.
    Retrieving schema at 'component_workflowTicket.xsd', relative to 'file:/E:/DIPPW
    F/XMLSchema/workflowSaveCreateProfile.xsd'.
    *[ERROR] More than one part for message OblixIDXMLInput*
    org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException:
    More than one part for message OblixIDXMLInput
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
    ence(WSDL11ToAxisServiceBuilder.java:1162)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
    ence(WSDL11ToAxisServiceBuilder.java:1085)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateBindi
    ng(WSDL11ToAxisServiceBuilder.java:686)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
    int(WSDL11ToAxisServiceBuilder.java:538)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
    ints(WSDL11ToAxisServiceBuilder.java:489)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
    ce(WSDL11ToAxisServiceBuilder.java:363)
    at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateA
    llServices(WSDL11ToAllAxisServicesBuilder.java:107)
    at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerat
    ionEngine.java:147)
    at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
    at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
    Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException
    : Error parsing WSDL
    at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerat
    ionEngine.java:153)
    at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
    at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
    Caused by: org.apache.axis2.AxisFault: More than one part for message OblixIDXML
    Input
    at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
    ce(WSDL11ToAxisServiceBuilder.java:397)
    at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateA
    llServices(WSDL11ToAllAxisServicesBuilder.java:107)
    at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerat
    ionEngine.java:147)
    ... 2 more
    Caused by: org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessin
    gException: More than one part for message OblixIDXMLInput
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
    ence(WSDL11ToAxisServiceBuilder.java:1162)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
    ence(WSDL11ToAxisServiceBuilder.java:1085)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateBindi
    ng(WSDL11ToAxisServiceBuilder.java:686)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
    int(WSDL11ToAxisServiceBuilder.java:538)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
    ints(WSDL11ToAxisServiceBuilder.java:489)
    at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
    ce(WSDL11ToAxisServiceBuilder.java:363).
    Thanks in advance.
    akshay

    Hello,
    Were you able to resolve this issue ?
    I am seeing the same issue and at my wits end.
    regards
    Amit

  • XMLBean generation from WSDL file

    I have used workshop for weblogic 9.2 to generate web service from wsdl files. The problem is however, that the (XmlBean) code generated from the <wsdl:fault name="..... /> does not genetate a "Throwable" object. The resulting methods produced by the Web Services -> Generate Web Service... menu option produces code that cannot be compiled, because the (generated) throws clause uses an object that is not derived from Throwable.
    Has anyone else had these symptoms? is there a fix?
    Thanks
    Alan

    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

  • Generatin client stubs from wsdl file

    i user wsimport to generate the client stubs
    look like i am missing some files
    like the service port/stub..
    please help

    i user wsimport to generate the client stubs
    look like i am missing some files
    like the service port/stub..wsimport is run on a WSDL and it generates all required stubs for you. What is the exact nature of your problem ? more details please

  • ABAP client proxy from WSDL

    I have 2 problems in creating abap client proxies using wsdl
    1.when i try to create client proxy by giving RPC style wsdl(generated by SAP itself for a RFC) the system throws an error and not allowing to create the proxy
    2.The client proxy which i have created for a wsdl(either SAP created document type/any wsdl from commercial websites) gives an error "No receiver could be found"
    could somebody please clarify and help me to solve the problem.
    Thanks in advance.
    Vasanth.

    Hi Vasanth,
    There are many threads and blogs on this topic.
    Choose the search Forum on the Forum page and select "All categories" in the Category field and enter your topic "ABAP client proxy from WSDL" in the search field.
    Rgds,
    Sam Raju

  • I am facing problem while reading values from properties file ...i am getting null pointer exception earlier i was using jdeveloper10g now i am using 11g

    i am facing problem while reading values from properties file ...i am getting null pointer exception earlier i was using jdeveloper10g now i am using 11g

    hi TimoHahn,
    i am getting following exception in JDeveloper(11g release 2) Studio Edition Version 11.1.2.4.0 but it works perfectly fine in JDeveloper 10.1.2.1.0
    Root cause of ServletException.
    java.lang.NullPointerException
    at java.util.PropertyResourceBundle.handleGetObject(PropertyResourceBundle.java:136)
    at java.util.ResourceBundle.getObject(ResourceBundle.java:368)
    at java.util.ResourceBundle.getString(ResourceBundle.java:334)
    at org.rbi.cefa.master.actionclass.UserAction.execute(UserAction.java:163)
    at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
    at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
    at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
    at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
    at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:119)
    at java.security.AccessController.doPrivileged(Native Method)
    at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:315)
    at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:442)
    at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:103)
    at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:171)
    at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:139)
    at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun(WebAppServletContext.java:3715)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3681)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2277)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2183)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1454)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)

  • 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

  • Clientgen in WL 81 giving problems for stub generation from WL91 WSDL

    Hi,
    I am very new to this forum and new to Weblogic too.
    Here is my problem. I generated a webservice from a Stateless Session bean using annotation in WebLogic 91. Used the "jwsc"/"wldeploy" to generate and deploy the webservice. Also generated the client stubs using "clientgen" in weblogic 91.
    Created a small web application using a single jsp and servlet (the servlet is where i invoke the service).
    Everything works fine till its weblogic 91.
    Now the problem. I need to make the jsp work from Weblogic 81. So I am trying to create the client stubs from the service endpoint WSDL on WebLogic 91 by using the deployed webservice URL.
    The clientgen in WL 81 is complaining that the "parameters" is already defined (Please see the error below".
    I would assume that BEA would have tested this scenario as it should be a no-brainer. So why does the cleintgen in WL 81 complain. Is there any other step or way that I am missing. I have tried all sorts of things before posting to this forum (like 1. generating the stubs using WSDL2JAVA using axis -- WebLogic 81 gives a null pointer exception 2. generating the client stubs using "clientgen" in WL 91 and trying to compile using the jdk 1.4 and using in WL 81 -- complains that the couldnot find something like jax-rpc._._.ServiceImpl
    Will be realy helpful if someone who had this kind of experience of someone from BEA can help me a little bit.
    Thanks in advance to all for your time.
    ERROR WHILE using CLIENGEN
    build-client:
    [clientgen] Generating client jar for http://localhost:7001/webservice/MAC/Metho
    dsAccessControl?WSDL ...
    [clientgen] WARNING: Map ['http://elexnet.bah.com/methods']:ArrayOfint_literal i
    ncompliantly with JAX-RPC, mapping to a Java array of .int
    [clientgen] WARNING: Map ['http://elexnet.bah.com/methods']:ArrayOfMethodUserTO_
    literal incompliantly with JAX-RPC, mapping to a Java array of com.bah.elexnet.s
    erver.to.MethodUserTO
    [clientgen] C:\Documents and Settings\525328.ROCKIT\Local Settings\Temp\test.jar
    198043065\com\bah\elexnet\methods\client\accesscontrol\MACSPortType.java:15: par
    ameters is already defined in unArchiveUser(com.bah.elexnet.methods.UnArchiveUse
    r,com.bah.elexnet.methods.holders.UnArchiveUserResponseHolder)
    [clientgen] public void unArchiveUser(com.bah.elexnet.methods.UnArchiveUser pa
    rameters, com.bah.elexnet.methods.holders.UnArchiveUserResponseHolder parameters
    [clientgen]
    ^
    [clientgen] C:\Documents and Settings\525328.ROCKIT\Local Settings\Temp\test.jar
    198043065\com\bah\elexnet\methods\client\accesscontrol\MACSPortType.java:21: par
    ameters is already defined in editUserRoles(com.bah.elexnet.methods.EditUserRole
    s,com.bah.elexnet.methods.holders.EditUserRolesResponseHolder)
    [clientgen] public void editUserRoles(com.bah.elexnet.methods.EditUserRoles pa
    rameters, com.bah.elexnet.methods.holders.EditUserRolesResponseHolder parameters
    [clientgen]
    ^
    [clientgen] C:\Documents and Settings\525328.ROCKIT\Local Settings\Temp\test.jar
    198043065\com\bah\elexnet\methods\client\accesscontrol\MACSPortType.java:27: par
    ameters is already defined in getUsers(com.bah.elexnet.methods.GetUsers,com.bah.
    elexnet.methods.holders.GetUsersResponseHolder)
    [clientgen] public void getUsers(com.bah.elexnet.methods.GetUsers parameters,
    com.bah.elexnet.methods.holders.GetUsersResponseHolder parameters)
    [clientgen]
    ^
    [clientgen] C:\Documents and Settings\525328.ROCKIT\Local Settings\Temp\test.jar
    198043065\com\bah\elexnet\methods\client\accesscontrol\MACSPortType.java:33: par
    ameters is already defined in addUserRoles(com.bah.elexnet.methods.AddUserRoles,
    com.bah.elexnet.methods.holders.AddUserRolesResponseHolder)
    [clientgen] public void addUserRoles(com.bah.elexnet.methods.AddUserRoles para
    meters, com.bah.elexnet.methods.holders.AddUserRolesResponseHolder parameters)
    [clientgen]
    ^
    [clientgen] C:\Documents and Settings\525328.ROCKIT\Local Settings\Temp\test.jar
    198043065\com\bah\elexnet\methods\client\accesscontrol\MACSPortType.java:39: par
    ameters is already defined in archiveUser(com.bah.elexnet.methods.ArchiveUser,co
    m.bah.elexnet.methods.holders.ArchiveUserResponseHolder)
    [clientgen] public void archiveUser(com.bah.elexnet.methods.ArchiveUser parame
    ters, com.bah.elexnet.methods.holders.ArchiveUserResponseHolder parameters)
    [clientgen]
    ^
    [clientgen] C:\Documents and Settings\525328.ROCKIT\Local Settings\Temp\test.jar
    198043065\com\bah\elexnet\methods\client\accesscontrol\MACSPortType.java:45: par
    ameters is already defined in changeSystemPassword(com.bah.elexnet.methods.Chang
    eSystemPassword,com.bah.elexnet.methods.holders.ChangeSystemPasswordResponseHold
    er)
    [clientgen] public void changeSystemPassword(com.bah.elexnet.methods.ChangeSys
    temPassword parameters, com.bah.elexnet.methods.holders.ChangeSystemPasswordResp
    onseHolder parameters)
    [clientgen]
    ^
    [clientgen] C:\Documents and Settings\525328.ROCKIT\Local Settings\Temp\test.jar
    198043065\com\bah\elexnet\methods\client\accesscontrol\MACSPortType.java:51: par
    ameters is already defined in deleteUser(com.bah.elexnet.methods.DeleteUser,com.
    bah.elexnet.methods.holders.DeleteUserResponseHolder)
    [clientgen] public void deleteUser(com.bah.elexnet.methods.DeleteUser paramete
    rs, com.bah.elexnet.methods.holders.DeleteUserResponseHolder parameters)
    [clientgen]
    ^
    [clientgen] C:\Documents and Settings\525328.ROCKIT\Local Settings\Temp\test.jar
    198043065\com\bah\elexnet\methods\client\accesscontrol\MACSPortType.java:57: par
    ameters is already defined in getUserRoles(com.bah.elexnet.methods.GetUserRoles,
    com.bah.elexnet.methods.holders.GetUserRolesResponseHolder)
    [clientgen] public void getUserRoles(com.bah.elexnet.methods.GetUserRoles para
    meters, com.bah.elexnet.methods.holders.GetUserRolesResponseHolder parameters)
    [clientgen]
    ^
    [clientgen] C:\Documents and Settings\525328.ROCKIT\Local Settings\Temp\test.jar
    198043065\com\bah\elexnet\methods\client\accesscontrol\MACSPortType_Stub.java:20
    : parameters is already defined in unArchiveUser(com.bah.elexnet.methods.UnArchi
    veUser,com.bah.elexnet.methods.holders.UnArchiveUserResponseHolder)
    [clientgen] public void unArchiveUser(com.bah.elexnet.methods.UnArchiveUser pa
    rameters, com.bah.elexnet.methods.holders.UnArchiveUserResponseHolder parameters
    [clientgen]
    ^
    [clientgen] C:\Documents and Settings\525328.ROCKIT\Local Settings\Temp\test.jar
    198043065\com\bah\elexnet\methods\client\accesscontrol\MACSPortType_Stub.java:39
    : parameters is already defined in editUserRoles(com.bah.elexnet.methods.EditUse
    rRoles,com.bah.elexnet.methods.holders.EditUserRolesResponseHolder)
    [clientgen] public void editUserRoles(com.bah.elexnet.methods.EditUserRoles pa
    rameters, com.bah.elexnet.methods.holders.EditUserRolesResponseHolder parameters
    [clientgen]
    ^
    [clientgen] C:\Documents and Settings\525328.ROCKIT\Local Settings\Temp\test.jar
    198043065\com\bah\elexnet\methods\client\accesscontrol\MACSPortType_Stub.java:58
    : parameters is already defined in getUsers(com.bah.elexnet.methods.GetUsers,com
    .bah.elexnet.methods.holders.GetUsersResponseHolder)
    [clientgen] public void getUsers(com.bah.elexnet.methods.GetUsers parameters,
    com.bah.elexnet.methods.holders.GetUsersResponseHolder parameters)
    [clientgen]
    ^
    [clientgen] C:\Documents and Settings\525328.ROCKIT\Local Settings\Temp\test.jar
    198043065\com\bah\elexnet\methods\client\accesscontrol\MACSPortType_Stub.java:77
    : parameters is already defined in addUserRoles(com.bah.elexnet.methods.AddUserR
    oles,com.bah.elexnet.methods.holders.AddUserRolesResponseHolder)
    [clientgen] public void addUserRoles(com.bah.elexnet.methods.AddUserRoles para
    meters, com.bah.elexnet.methods.holders.AddUserRolesResponseHolder parameters)
    [clientgen]
    ^
    [clientgen] C:\Documents and Settings\525328.ROCKIT\Local Settings\Temp\test.jar
    198043065\com\bah\elexnet\methods\client\accesscontrol\MACSPortType_Stub.java:96
    : parameters is already defined in archiveUser(com.bah.elexnet.methods.ArchiveUs
    er,com.bah.elexnet.methods.holders.ArchiveUserResponseHolder)
    [clientgen] public void archiveUser(com.bah.elexnet.methods.ArchiveUser parame
    ters, com.bah.elexnet.methods.holders.ArchiveUserResponseHolder parameters)
    [clientgen]
    ^
    [clientgen] C:\Documents and Settings\525328.ROCKIT\Local Settings\Temp\test.jar
    198043065\com\bah\elexnet\methods\client\accesscontrol\MACSPortType_Stub.java:11
    5: parameters is already defined in changeSystemPassword(com.bah.elexnet.methods
    .ChangeSystemPassword,com.bah.elexnet.methods.holders.ChangeSystemPasswordRespon
    seHolder)
    [clientgen] public void changeSystemPassword(com.bah.elexnet.methods.ChangeSys
    temPassword parameters, com.bah.elexnet.methods.holders.ChangeSystemPasswordResp
    onseHolder parameters)
    [clientgen]
    ^
    [clientgen] C:\Documents and Settings\525328.ROCKIT\Local Settings\Temp\test.jar
    198043065\com\bah\elexnet\methods\client\accesscontrol\MACSPortType_Stub.java:13
    4: parameters is already defined in deleteUser(com.bah.elexnet.methods.DeleteUse
    r,com.bah.elexnet.methods.holders.DeleteUserResponseHolder)
    [clientgen] public void deleteUser(com.bah.elexnet.methods.DeleteUser paramete
    rs, com.bah.elexnet.methods.holders.DeleteUserResponseHolder parameters)
    [clientgen]
    ^
    [clientgen] C:\Documents and Settings\525328.ROCKIT\Local Settings\Temp\test.jar
    198043065\com\bah\elexnet\methods\client\accesscontrol\MACSPortType_Stub.java:15
    3: parameters is already defined in getUserRoles(com.bah.elexnet.methods.GetUser
    Roles,com.bah.elexnet.methods.holders.GetUserRolesResponseHolder)
    [clientgen] public void getUserRoles(com.bah.elexnet.methods.GetUserRoles para
    meters, com.bah.elexnet.methods.holders.GetUserRolesResponseHolder parameters)
    [clientgen]
    ^
    [clientgen] 16 errors
    [clientgen] java.io.IOException: Compiler failed executable.exec
    [clientgen] at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(Comp
    ilerInvoker.java:470)
    [clientgen] at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvok
    er.java:328)
    [clientgen] at weblogic.utils.compiler.CompilerInvoker.compile(CompilerInvok
    er.java:336)
    [clientgen] at weblogic.webservice.tools.build.internal.CompilerHelper.compi
    leFiles(CompilerHelper.java:80)
    [clientgen] at weblogic.webservice.tools.build.internal.ClientGenImpl.compil
    eStubs(ClientGenImpl.java:627)
    [clientgen] at weblogic.webservice.tools.build.internal.ClientGenImpl.genera
    teStub(ClientGenImpl.java:572)
    [clientgen] at weblogic.webservice.tools.build.internal.ClientGenImpl.doClie
    ntGenFromWsdl(ClientGenImpl.java:409)
    [clientgen] at weblogic.webservice.tools.build.internal.ClientGenImpl.run(Cl
    ientGenImpl.java:340)
    [clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.doC
    lientGen(ClientGenTask.java:351)
    [clientgen] at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.exe
    cute(ClientGenTask.java:208)
    [clientgen] at org.apache.tools.ant.Task.perform(Task.java:341)
    [clientgen] at org.apache.tools.ant.Target.execute(Target.java:309)
    [clientgen] at org.apache.tools.ant.Target.performTasks(Target.java:336)
    [clientgen] at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
    [clientgen] at org.apache.tools.ant.Project.executeTargets(Project.java:1255
    [clientgen] at org.apache.tools.ant.Main.runBuild(Main.java:609)
    [clientgen] at org.apache.tools.ant.Main.start(Main.java:196)
    [clientgen] at org.apache.tools.ant.Main.main(Main.java:235)
    BUILD FAILED
    file:C:/Projects/OtherProjects/WL/soaws/build/build.xml:122: weblogic.webservice
    .tools.build.WSBuildException: Compiler failed executable.exec - with nested exc
    eption:
    [java.io.IOException: Compiler failed executable.exec]

    did you get a solution for this issue. I am trying to generate a stub to connect to a webservice i created by exposing my stateless session EJB as a web service, using annotations. I want to create a client stub using the clientgen from weblogic 81. I am unable to do this, do you have any solution to this.

  • Webservice client generated from WSDL null entity problem

    hi,
    I'am having a serious problem using the generation (data centric development) capability of Flash builder.
    I have a simple XSD and generated WSLD (from Spring Framework using JAXB). In this I have defined an UpdateRelatie function.
    It looks something like this:
        <xsd:element name="UpdateRelatieRequest">
            <xsd:complexType>
                 <xsd:sequence>
                    <xsd:element name="relatie" type="relatie" minOccurs="1" maxOccurs="1"/>
                </xsd:sequence>
            </xsd:complexType>
        </xsd:element>
        <xsd:element name="UpdateRelatieResponse">
            <xsd:complexType>
                <xsd:sequence>
                    <xsd:element name="relatie" type="relatie" minOccurs="1" maxOccurs="1"/>
                </xsd:sequence>
            </xsd:complexType>
        </xsd:element>
        <xsd:complexType name="relatie">
            <xsd:sequence>
                <xsd:element name="id" type="xsd:int" />
                <xsd:element name="naam" type="xsd:string" />
                <xsd:element name="telefoonNummer" type="xsd:string" />
                <xsd:element name="mobielNummer" type="xsd:string" />
                <xsd:element name="email" type="xsd:string" />
                <xsd:element name="rekeningNummer" type="xsd:string" />
                <xsd:element name="btwNummer" type="xsd:string" />
                <xsd:element name="kvkNummer" type="xsd:string" />
                <xsd:element name="actief" type="xsd:boolean" />
            </xsd:sequence>
        </xsd:complexType>
    My generated WSDL looks something like this (for the update part as show above).
    <?xml version="1.0" encoding="UTF-8" standalone="no"?><wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:schema="http://www.mydomain.nl/gbs/service/ws" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" targetNamespace="http://www.mydomain.nl/gbs/service/ws">
      <wsdl:types>
        <xsd:schema xmlns="http://www.mydomain.nl/gbs/service/ws" xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.mydomain.nl/gbs/service/ws">
      [excluded xsd.. see above]
    </xsd:schema>
      </wsdl:types>
      <wsdl:message name="UpdateRelatieRequest">
        <wsdl:part element="schema:UpdateRelatieRequest" name="UpdateRelatieRequest">
        </wsdl:part>
      </wsdl:message>
      <wsdl:message name="UpdateRelatieResponse">
        <wsdl:part element="schema:UpdateRelatieResponse" name="UpdateRelatieResponse">
        </wsdl:part>
      </wsdl:message>
       <wsdl:portType name="Relatie">
        <wsdl:operation name="UpdateRelatie">
          <wsdl:input message="schema:UpdateRelatieRequest" name="UpdateRelatieRequest">
        </wsdl:input>
          <wsdl:output message="schema:UpdateRelatieResponse" name="UpdateRelatieResponse">
        </wsdl:output>
        </wsdl:operation>
      </wsdl:portType>
      <wsdl:binding name="RelatieBinding" type="schema:Relatie">
        <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
        <wsdl:operation name="UpdateRelatie">
          <soap:operation soapAction=""/>
          <wsdl:input name="UpdateRelatieRequest">
            <soap:body use="literal"/>
          </wsdl:input>
          <wsdl:output name="UpdateRelatieResponse">
            <soap:body use="literal"/>
          </wsdl:output>
        </wsdl:operation>
      </wsdl:binding>
      <wsdl:service name="RelatieService">
        <wsdl:port binding="schema:RelatieBinding" name="RelatiePort">
          <soap:address location="http://localhost:8080/GBS/relatieService"/>
        </wsdl:port>
      </wsdl:service>
    </wsdl:definitions>
    When I run my test client written in Java, I can update any given relatie-object in my database.
    BUT when I, based upon this, generate a webservice stub using the "data -> connect to webservice" option. I get nicely generated code and the ability to to bind this to an form with which I can edit the data.
    Now for my PROBLEM:
    When I enter data in the form, during the process of transforming my Relatie object to XML, my entire object disappears. i.e. my object does NOT get transformed to XML for soap transport. Somewhere deep in the webservice code, it just gets ignored and I do NOT know why.
    What does work is retrieving data through a webservice. I can display a nice grid full of data from my database. What does not work is trying to send a domain object (Relatie) from Flex through a webservice and process it in java. The object is null on the java side. I can even see in the resulting soap envelope that nothing gets transformed to XML. See output below:
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
                       xmlns:xsd="http://www.w3.org/2001/XMLSchema"
                       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> 
      <SOAP-ENV:Body>   
        <schema:UpdateRelatieRequest xmlns:schema="http://www.mydomain.nl/gbs/service/ws"/>  <!-- NO OBJECT -->
      </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    Which should have been based upon the given WSDL (as the java client does send over the wire)
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Body>
      <ns3:InsertRelatieRequest xmlns:ns3="http://www.mydomain.nl/gbs/service/ws">
        <relatie>
          <btwNummer>BTW</btwNummer>                                                                                            <!-- OBJECT PRESENT -->
          <actief>false</actief>
       </relatie>
      </ns3:InsertRelatieRequest>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    Can anyone help me please. I'am stuck now.
    Kind regards,
    Marc

    Thanks for the detailed steps. I was able to reproduce the issue.
    I have logged an issue under 'WebService'. https://bugs.adobe.com/jira/browse/SDK-24841 . We will look into it.
    -Radhakrishna

  • Client API generation from WSDL.

    Hi,
    Could any one guide as how to generate the client from WSDL? I am using RAD7/Eclipse.
    When i try to generate it gives below error.
    Errors occurred during wsimport.
      warning: src-resolve.4.2: Error resolving component 'ns1:pagedata'. It was detected that 'ns1:pagedata' is in namespace 'urn:SCenter-Data-Svc-SubmissionWorkflowSvc:CreateSubmissionWorkItemRequest', but components from this namespace are not referenceable from schema document 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema8'. If this is the incorrect namespace, perhaps the prefix of 'ns1:pagedata' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema8'.
      line 0 of file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema8
    warning: src-resolve.4.2: Error resolving component 'ns2:pagedata'. It was detected that 'ns2:pagedata' is in namespace 'urn:SCenter-Data-Svc-SubmissionWorkflowSvc:CreateSubmissionWorkItemResponse', but components from this namespace are not referenceable from schema document 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema8'. If this is the incorrect namespace, perhaps the prefix of 'ns2:pagedata' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema8'.
      line 0 of file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema8
    warning: src-resolve.4.2: Error resolving component 'ns3:pagedata'. It was detected that 'ns3:pagedata' is in namespace 'urn:SCenter-Data-Svc-BrokerInfo:pyDefault', but components from this namespace are not referenceable from schema document 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1'. If this is the incorrect namespace, perhaps the prefix of 'ns3:pagedata' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1'.
      line 0 of file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1
    warning: src-resolve.4.2: Error resolving component 'ns4:pagedata'. It was detected that 'ns4:pagedata' is in namespace 'urn:SCenter-Data-Svc-ClientInfo:pyDefault', but components from this namespace are not referenceable from schema document 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1'. If this is the incorrect namespace, perhaps the prefix of 'ns4:pagedata' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1'.
      line 0 of file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1
    warning: src-resolve.4.2: Error resolving component 'ns5:pagedata'. It was detected that 'ns5:pagedata' is in namespace 'urn:SCenter-Data-Svc-State:pyDefault', but components from this namespace are not referenceable from schema document 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1'. If this is the incorrect namespace, perhaps the prefix of 'ns5:pagedata' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1'.
      line 0 of file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1
    warning: src-resolve.4.2: Error resolving component 'ns6:pagedata'. It was detected that 'ns6:pagedata' is in namespace 'urn:SCenter-Data-Svc-SubmissionInfo:pyDefault', but components from this namespace are not referenceable from schema document 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1'. If this is the incorrect namespace, perhaps the prefix of 'ns6:pagedata' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1'.
      line 0 of file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema1
    warning: src-resolve.4.2: Error resolving component 'ns7:pagedata'. It was detected that 'ns7:pagedata' is in namespace 'urn:SCenter-Data-Svc-Exception:pyDefault', but components from this namespace are not referenceable from schema document 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema2'. If this is the incorrect namespace, perhaps the prefix of 'ns7:pagedata' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema2'.
      line 0 of file:/C:/rad7/workspace/WebService/WebContent/META-INF/com/Submissions.WSDL#types?schema2
    error: Invalid header "ServiceInvoker" of binding operation "CreateSubmissionWorkItem": not literal
      Invalid header "ServiceInvoker" of binding operation "CreateSubmissionWorkItem": not literalCan any one tell us what is happening?

    just like the error message says, you are using some namespaces in your wsdl, e.g. "urn:SCenter-Data-Svc-SubmissionWorkflowSvc:CreateSubmissionWorkItemRequest" for which there is no relevant schema import. thus, the code generator cannot find the definition of the types in those namespaces.

  • 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.

  • Problem with old namespace in WSDL file

    I have a problem with my WSDL file.  My scenario is SOAP to IDOC. 
    Originally the ESB data types were configured under namespace urn:test1:xxx  for development purposes.  When it came time to implement and test, we copied the data types from the old name space to a new namespace http://company.com:interface.
    After the new objects were created, all the old test objects were deleted, including the old namespace definition.  Now when I generate the WSDL file, the top part of the WSDL file looks correct, but toward the bottom, there are references to the old namespace.
    Does anyone know why these reference are appearing, and is there any way to correct this without deleting all my objects and rebuilding everything?
    Thanks in advance for any help.  Will award points for help.
    Terri

    Found the problem....the XML namespace in the Message type still contained the old namespace.  When this was changed to the new namespace, second target namespace was no longer generated.

  • How client will give WSDL File to PI

    Hi,
    My scenario is webservice to SAP and using SAP 7.1.
    I have following doubts.Request you to clarify on this.
    1.The way client is going to provide WSDL to PI 7.1. I know that they will be giving WSDL by sending mail,giving URL. and i would like to know other alternate posbbile ways to get WSDL from them.
    2. Approach to be followed by the client  to trigger the WSDL request (ex: SOAP GUI).
    appreciate your help.
    Thanks
    Hamja

    Hi Hamja,
    What you have understand is the difference between:
    - When you use a sender SOAP Adapter, in this case.. you publish the webservice to be hosted in your PI server; so, you generate the URL and the WSDL File. And you give this file to everyone who wants to consume that WS.
    For example, an interfaces that is WS -> PI -> RFC. (Sync Communication)
    - And in the other case, is when is a receiver SOAP. With this scenario, and external party provides you a WSDL and a URL in order to PI invoke that URL to be the consumer of the WebService.
    Example: RFC ->  PI  -> WS  (Sync Communication)
    Which scenario are you going to do?
    rgds

  • Java implementation from WSDL file

    Hello All
    I am working on my thesis and have to deal with web services. I have a WSDL file where I have to create the Java implementation for and deploy it to TomCat which is comming with JWSDP1.3.
    The steps I do are as follow:
    1. Get the WSDL file
    2. Create the config.xml file
    3. run wscompile with "-import" option
    4. implement service implementation (provider interface)
    5. run wsdeploy tool
    All tools are running successfully without exception. When I try to access the webservice I receive the following message from tomcat:
    "No JAX-RPC context information available."
    and I cannot access the webservice from my client program. The "hello" example works with my setup.
    Below, please find my WSDL file and my config file as well as my provider interface implementation.
    Thanks for your help.
    ===========
    calculatesqrt1.wsdl:
    <definitions xmlns:tns="http://localhost:8080/calculatesqrt1-jaxrpc1/ws/calcultesqrt1.wsdl" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" targetNamespace="http://localhost:8080/calculatesqrt1-jaxrpc1/ws/calcultesqrt1.wsdl" name="Calculatesqrt1">
         <types/>
         <message name="CalculatesqrtProvider1_sqrt">
              <part name="double_1" type="xsd:double"/>
         </message>
         <message name="CalculatesqrtProvider1_sqrtResponse">
              <part name="result" type="xsd:double"/>
         </message>
         <portType name="CalculatesqrtProvider1">
              <operation name="sqrt" parameterOrder="double_1">
                   <input message="tns:CalculatesqrtProvider1_sqrt"/>
                   <output message="tns:CalculatesqrtProvider1_sqrtResponse"/>
              </operation>
         </portType>
         <binding name="CalculatesqrtProvider1Binding" type="tns:CalculatesqrtProvider1">
              <soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
              <operation name="sqrt">
                   <input>
                        <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://localhost:8080/calculatesqrt1-jaxrpc1/ws/calculatesqrt1.wsdl"/>
                   </input>
                   <output>
                        <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://localhost:8080/calculatesqrt1-jaxrpc1/ws/calculatesqrt1.wsdl"/>
                   </output>
                   <soap:operation/>
              </operation>
         </binding>
         <service name="Calculatesqrt1">
              <port name="CalculatesqrtProvider1Port" binding="tns:CalculatesqrtProvider1Binding">
                   <soap:address location="http://localhost:8080/calculatesqrt1-jaxrpc1/ws/calcultesqrt1"/>
              </port>
         </service>
    </definitions>
    ===========
    config.xml:
    <?xml version="1.0" encoding="UTF-8"?>
    <configuration xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
         <wsdl location="Calculatesqrt1.wsdl" packageName="calcusqrt1">
         </wsdl>
    </configuration>
    ============
    CalculatesqrtServiceImpl1.java:
    package calcusqrt1;
    public class CalculatesqrtServiceImpl1 implements calcusqrt1.CalculatesqrtProvider1 {
      public double sqrt(double double0) {
        return Math.sqrt(double0);

    Please post future JAXRPC related questions to [email protected]
    Sounds like it did not get deployed properly on the web server. You should be able to hit the URL for the
    web service in a web browser to get an information.
    The client will use the address stored in the WSDL to access the webservice, please make sure that it is correct. If you download the WSDL from the deployed service the address should be fixed up for you.

  • Problems connecting Client 9i from vb6

    Hi, ive got an app, which connects to Oracle Client 9i from vb6 using ADO, the problem is that in some client machines i can connect with OraOleDB.Oracle.1 Provider (including mine) but in the others just got a sucessfull connection with MSDAORA provider and i dont know why..
    Can anyone help me in order to use just one provider, thanks

    Hello,
    You must set DNS client on windows (or host name in hosts file)
    regards

Maybe you are looking for

  • AT NEW in loops

    Hi everyone I have an internal sorted table (itab1) which contains data from table VBAP based on a unique key using VBELN and POSNR. I want to extract the first row for each VBELN into a seperate hashed table (itab2) with a key of VBELN.  Two restric

  • Error when launch HFM Demo

    I am getting this error when I launch HFM demo - Could not find a Hyperion Reporting and Analysis server running on demodrive.oracle.com at port 6800. Please verify your server connect string and confirm that the server is up. I have started all scri

  • Who wants a Small Ottoman Rug or Turkish candy as A Gift after a littler help? :)

    Hi Masters; Well,the headline,was little seductive,but when i tell my story,you ll understand me.I am a young entrepreneur from Turkey as i mentioned,studying architecture,and i have a dream about generate my own worldwide decoration brand,i have the

  • Thunderbolt and Hdmi Dual Screen MACMINI problem

    Hi there, I have two screens, one connected via HDMI, and another via Thunderbolt, which goes into thru UA APOLLO audio interface's 2nd thunderbolt output, when my Mac Mini starts up it is fine, for around 5 minutes, but then the thunderbolt display

  • JTextPane in JScrollPane... Scrolling when needed

    Hello all. I have a jtextpane in a jscrollpane and I'm using the following code to append a line in jtextpane and set the vertical scrollbar of jscrollpane at the bottom...   htmlDoc = (HTMLDocument) output.getDocument();   htmlKit.insertHTML(htmlDoc