HUGE PROBLEM: xsd:import generates invalid WSDL during deploy (11.1.1.3.0)

Hi,
I have a big problem:
if I create a bpel/mediator based on XSDs that use xsd:import, like this:
<xsd:import schemaLocation="./Generic.xsd" namespace="http://test.mydomain.com/test/Generic"/>
when i deploy, I get an error trying to test the service using oracle EM.
THe error looks like:
Either the WSDL URL is invalid or the WSDL file is not valid or incorrect. - java.io.IOException: WSDLException: faultCode=OTHER_ERROR: Lettura di WSDL da http://dev-oraclevmmac:8001/soa-infra/services/default/TestSOAProject/bpelprocess2_client_ep?XSD=./xsd/Test.xsd non riuscita: WSDL non trovato
What can I do ?

Yes, of course XSD and WSDL are valid inside JDev. I validated them also using XMLSpy.
The problem is that the WSDL becomes invalid through deployment.
But, after some hour of investigation, I've come to a solution: I have to puth the ABSOLUTE PATH ('relative' to the .bpel file) inside each xsd:import and inside wsdls.
So, my example is now:
<xsd:import schemaLocation="../xsd/Generic.xsd" namespace="http://test.mydomain.com/test/Generic"/>

Similar Messages

  • Huge problems with my MacBook:  Invalid Node Structure and More!

    A couple days ago I was browsing the internet, and when I closed Safari, the system froze. I couldn't even force quit out of anything, so I had to shut it off manually. When I tried to turn my computer back on the next day, I couldn't get past the Apple screen. The little wheel would keep spinning, but I could never get anywhere.
    Then, I tried to boot from the Leopard DVD to possibly reinstall Leopard, hoping it would work. At first, no drives would show up to install to, but for some reason, they eventually showed up. Problem is, I don't have enough free memory to reinstall Leopard. Furthermore, I've tried to fit it on the space I have, and it says that the install failed, so I can't reinstall Leopard.
    I also went to Disk Utility from the DVD and tried to repair the disk. The only option available was to Verify Disk, but when I go there, that fails, and it says "invalid node structure."
    I'm not sure what happened to my computer because it seemed to come from nowhere. To sum up, I cannot log in to OS X, or even XP on a separate partition, I can't reinstall Leopard, and I can't repair the disk. I've read about how DiskWarrior might help, but I can't get in to OS X. Does anyone have any idea what happened or what I can do? I haven't backed anything up, so if I'm screwed, then so be it, I guess. Just wondering if anyone has any explanations or suggestions. Thanks.

    Interesting how many people have this same issue. A friend of mine has brought me her white Macbook Intel Core 2 with Leopard and it had a folder with a question mark instead of the apple at startup. I was able to boot using the Mac Install DVD and ran Disk Utility. It said something like "Invalid Node Structure" and "Cannot Repair". Unfortunately DiskWarrior will not fix this. I tried it to no avail. I'm resigned to the fact that a new hard drive is necessary.
    The HD in there is a Hitachi 120GB.
    It also wouldn't let me erase the disk nor partition it. Then, one morning I woke up and it was able to erase! So I erased, then installed Tiger. It seemed to be working fine. So I rebooted from the Leopard drop-in disk and installed Leopard. Then I restarted, and BAM! back to the question mark folder. Now I'm back to where I started. Other threads
    I forgot to mention that my friend had photos and music on the HD that she couldn't do without and I was able to recover that data using Data Recover II. First I had to use SuperDuper to clone my own computer onto an external drive so I could use it as a boot drive.
    For now the only solution is to buy a new internal hard drive and reinstall the OS. And regularly backup!!
    So I guess this issue has not really been solved, but hopefully you have warranty. Unfortunately for my friend, this happened a week after her warranty expired.
    Good luck.

  • JAX-WS generated WSDL uses xsd:import and no option to inline schemas

    Is it possible to configure JAX-WS 2.0/2.1 so that when generating WSDL at runtime it will inline the schema definitions instead of using the <xsd:import> method? Unfortunately, some clients (Adobe Flex, for example) do NOT know how to process schema imports. I realize that Adobe (and others) should fix the problem on their end and become fully spec compliant, but the cold reality is that they are not.
    Any advice, suggestions, or solutions would be greatly appreciated.
    Regards,
    Todd

    You should post this question either to the JAXB 2.0 and JAX-WS 2.0 forum (http://forums.java.net/jive/forum.jspa?forumID=46) or the JAX-WS dev mailing list ([email protected]) so that the team is aware of the issue.
    That functionality currently does not exist. The only work around that I am aware of is to generate the WSDL before deployment and rearrange it as necessary.

  • Problem while Importing wsdl( Generated in XI) in Visual Studio

    Hello XPert's,
    I am working on a scenario where I have to call SAP XI web service in client .Net application using Visual Studio5.
    I have already generated my wsdl using SAP XI Web Service wizard.  Here is the part of my wsdl...
    <?xml version="1.0" encoding="ISO-8859-1"?>
    <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:p1="http://ccsd.net/sapr3/wm/manifest" name="MI_MULT_IMAGES" targetNamespace="http://ccsd.net/sapr3/wm/manifest">
         <wsdl:documentation>
         Message interface for outbound
         </wsdl:documentation>
         <wsdl:types>
              <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://ccsd.net/sapr3/wm/manifest" targetNamespace="http://ccsd.net/sapr3/wm/manifest">
                   <xsd:element name="MT_RECORD_MULTIPLE" type="SAVEIMAGE_MULTIPLE" />
                   <xsd:complexType name="SAVEIMAGE_MULTIPLE">
                        <xsd:annotation>
                             <xsd:appinfo source="http://sap.com/xi/TextID">
                             f3999640f96e11dcae470003bab2aa70
                             </xsd:appinfo>
                        </xsd:annotation>
                        <xsd:sequence>
                             <xsd:element name="DT_IMAGES" maxOccurs="unbounded">
                                  <xsd:annotation>
                                       <xsd:appinfo source="http://sap.com/xi/TextID">
                                       7b023f10f91011dca4280011439c56bd
                                       </xsd:appinfo>
                                  </xsd:annotation>
                                  <xsd:complexType>
                                       <xsd:sequence>
                                            <xsd:element name="ImageName" type="xsd:string">
                                                 <xsd:annotation>
                                                      <xsd:appinfo source="http://sap.com/xi/TextID">
                                                      7b023f11f91011dcb4b70011439c56bd
                                                      </xsd:appinfo>
                                                 </xsd:annotation>
                                            </xsd:element>
                                            <xsd:element name="ImageData" type="xsd:base64Binary">
                                                 <xsd:annotation>
                                                      <xsd:appinfo source="http://sap.com/xi/TextID">
                                                      7b023f12f91011dc9ded0011439c56bd
                                                      </xsd:appinfo>
                                                 </xsd:annotation>
                                            </xsd:element>
                                       </xsd:sequence>
                                  </xsd:complexType>
                             </xsd:element>
                        </xsd:sequence>
                   </xsd:complexType>
              </xsd:schema>
         </wsdl:types>
         <wsdl:message name="MT_RECORD_MULTIPLE">
              <wsdl:documentation>
              Message type
              </wsdl:documentation>
              <wsdl:part name="MT_RECORD_MULTIPLE" element="p1:MT_RECORD_MULTIPLE" />
         </wsdl:message>
         <wsdl:portType name="MI_MULT_IMAGES">
              <wsdl:operation name="MI_MULT_IMAGES">
                   <wsdl:output message="p1:MT_RECORD_MULTIPLE" />
              </wsdl:operation>
         </wsdl:portType>
         <ifr:properties xmlns:ifr="urn:com-sap:ifr:v2:wsdl">
              <ifr:category>
              ifmmessif
              </ifr:category>
              <ifr:methods>
                   <ifr:method name="MI_MULT_IMAGES">
                        <ifr:isSynchron>
                        false
                        </ifr:isSynchron>
                        <ifr:isInbound>
                        false
                        </ifr:isInbound>
                        <ifr:interfaceCategory>
                        outbound
                        </ifr:interfaceCategory>
                   </ifr:method>
              </ifr:methods>
              <ifr:messages>
                   <ifr:message name="MT_RECORD_MULTIPLE">
                        <ifr:messType>
                        ifmmessage
                        </ifr:messType>
                        <ifr:technicalNamespace>
                        http://ccsd.net/sapr3/wm/manifest
                        </ifr:technicalNamespace>
                   </ifr:message>
              </ifr:messages>
         </ifr:properties>
    </wsdl:definitions>
    However,
    Whenever I tried to import the wsdl in visual studio, it do not create / generate the classes for the element with maxoccurs="unbounded" ( here DT_IMAGES)...its just disappear...and makes diifficult for calling webservice-method in client application.
    Anybody has faced this problem before? there is any workaround for this?
    All help/suggestion would be highly appreciated.
    Thanks & Rgds,
    Nilesh

    Hi Nilesh,
    Can you try modifying your WSDL a bit by defining DT_IMAGES as  complex type directly in definition because your previous WSDL is causing ambiguity. It will not affect your message structure.Please see the BOLD Lines.
    <xsd:element name="MT_RECORD_MULTIPLE" type="SAVEIMAGE_MULTIPLE" />
    <xsd:complexType name="SAVEIMAGE_MULTIPLE">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    f3999640f96e11dcae470003bab2aa70
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:sequence>
    <xsd:complexType name="DT_IMAGES" maxOccurs="unbounded">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    7b023f10f91011dca4280011439c56bd
    </xsd:appinfo>
    </xsd:annotation>
    <xsd:sequence>
    <xsd:element name="ImageName" type="xsd:string">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    7b023f11f91011dcb4b70011439c56bd
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    <xsd:element name="ImageData" type="xsd:base64Binary">
    <xsd:annotation>
    <xsd:appinfo source="http://sap.com/xi/TextID">
    7b023f12f91011dc9ded0011439c56bd
    </xsd:appinfo>
    </xsd:annotation>
    </xsd:element>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    </wsdl:types>
    Regards,
    Piyush

  • Problem Import WSDL with XSD import Schema

    Hi SCN, i have problem
    I have a WSDL that references an xsd, but the structure is not visible in PI.
       <wsdl:types>
          <xsd:schema targetNamespace="http://tempuri.org/Imports">
             <xsd:import schemaLocation="http://bilbolab****.net/ServiceItemHO.svc?xsd=xsd0" namespace="http://tempuri.org/" />
             <xsd:import schemaLocation="http://bilbolab.****.net/ServiceItemHO.svc?xsd=xsd1" namespace="http://schemas.microsoft.com/2003/10/Serialization/" />
             <xsd:import schemaLocation="http://bilbolab.*****.net/ServiceItemHO.svc?xsd=xsd2" namespace="http://schemas.datacontract.org/2004/07/ItemHO.BO" />
          </xsd:schema>
       </wsdl:types>
       <wsdl:message name="iVistaHO_AddItemHO_InputMessage">
          <wsdl:part name="parameters" element="tns:AddItemHO" />
       </wsdl:message>
    WSDL works well using SoapUI.
    When imported to PI parameters is not displayed
    I Need Help
    Thank you.

    Hi, Dihiansan. I don't understand your proposal
    I need you see the structure in PI how in SoapUI.
    It is possible?
    Regards

  • 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

  • OpenTrans 2.1 .xsd import problem into PI 7.1

    Hello,
    While trying to import the latest version 2.1 of openTrans .xsd Files (I downloaded "openTRANS_2.1_german_all-in-one_package.zip") into PI 7.1 we fail. Error message while loading the file "opentrans_2_1.xsd" is:
    Unable to convert imported document to WSDL
    Reason:
    Unable to recognize document as valid XSDCheck selected category
    OpenTrans 1.0 we have already in use since several time, however there is a need for the latest version now.
    Has anybody managed to get openTrans 2.1 to work with PI 7.1? And if so - how?
    Thanks!
    Andreas

    Hello Andreas
    This error can occur if there is an element tag with the name XML, e.g.: <xsd:element name="xml">.  If the element name is something other than xml, e.g. <xsd:element name="test">, then the import should be ok.
    SAP does not allow the element name in an XSD to start with the prefix -   xml                                                                               
    This conforms to the xml schema standards set by W3C  i.e.  http://www.w3schools.com/xml/xml_elements.asp
    -> XML Naming Rules section.
    Also, check note #1255351 External Defintion - XSD Checks Problem
    Regards
    Mark

  • Error:Invalid WSDL URL While Importing Internet WSDL In Webdynpro

    Hi Everyone,
    I Am Facing Error While Importing Webservices in Webdynpro.
    https://usint.skire.com/ws/services/mainservice?wsdl
    The above WSDL I tried in Both Webservice Model and Adaptice Webservice Model.
    I Am Geeting Invalid WSDL URL.
    is any configuration required for https [SSL Webservices]Under Visual Admin Level.
    I Am Able To Consume the http Webservices in Internet www.webservicex.net
    In that site i took three webservices and i am able to cosnume all these tings in Webdynpro.
    The above https services i am facing the problem.
    Thanks
    SubbaRao

    Hi,Thanks For Reply,
    I Am getting the Invalid WSDL URL After Importing into Webdynpro.
    When I CHecked Under Wsnavigator Of Portal.
    i am getting below error
    Cannot download WSDL from https://usint.skire.com/ws/services/mainservice?wsdl: ERROR : Trying to resolve qualified base : DataHandler, but the uri resolver is not able to resolve the relevant namespace.
    Thanks
    SubbaRao

  • How to populate/import data in a XSD file generated from a webservice

    HI All,
      I have an XSD file generated from the webserive using the CRM FM E2C_DOWNLOAD_CRT_SCHEMA.
    I created a Adobe form with the Adobe life cycle designer using the XSD file.
    However Data will have to be entered manually in this adobe form and cannot be pre-populated with data, How do we pre-populate data in the Adobe form generated from XSD file of the above CRM FM.

    This is what you need:
    integer     li_fhandle, li_rcode = 1, li_sfound = 0, li_idx = 0, li_eqpos, i
    string ls_filename = 'C:\app.ini'
    string ls_line, as_key[], as_val[]
    string ls_section = '[General]'
    // OPEN INI FILE
    li_fhandle = FileOpen(ls_filename, LineMode!)
    IF IsNull(li_fhandle) OR li_fhandle < 1 THEN
      // DO NOTHING
    ELSE
      DO WHILE li_rcode > 0
      li_rcode = FileRead(li_fhandle, ls_line)
      IF li_rcode > 0 THEN
      IF POS(ls_section, ls_line) > 0 THEN
      li_sfound = 1
      CONTINUE
      END IF
      IF li_sfound = 0 THEN CONTINUE
      IF POS(ls_line, '[') > 0 AND POS(ls_line, ']') > 0 THEN EXIT
      li_eqpos = POS(ls_line, '=')
      li_idx++
      as_key[li_idx] = MID(ls_line, 1, li_eqpos - 1)
      as_val[li_idx] = MID(ls_line, li_eqpos + 1)
      END IF
      LOOP
    END IF
    FOR i = 1 TO li_idx
      messagebox('Key - Value',as_key[i] + ' = ' + as_val[i])
    NEXT
    // CLOSE INI FILE
    IF li_fhandle > 0 THEN
       FileClose(li_fhandle)
    END IF
    Adapt it to your needs... you probably should make it a function.

  • Wsdl problem with jwsc generated webservice

    Hi,
    I am generating a new webservice with the jwsc command and annotations (only one method at this point, "getDescripteurCourt"). The war file is correctly generated and I can deploy it without problenmes in WLS 10.0
    However, when use the webservice test page, I receive the following error
    http://localhost:7001/communWS/communwebservices?WSDL
    failed due to org.jdom.IllegalAddException: The namespace xmlns:="http://saac.ssq.local/commun" could not be added as content to "getDescripteurCourt": The namespace prefix "" collides with the element namespace prefix
    Here is my wsdl file generated by the jwsc command
    <?xml version='1.0' encoding='ISO-8859-1'?>
    <s0:definitions name="communwebservicesDefinitions" targetNamespace="http://saac.ssq.local/commun" xmlns="" xmlns:s0="http://schemas.xmlsoap.org/wsdl/" xmlns:s1="http://saac.ssq.local/commun" xmlns:s2="http://schemas.xmlsoap.org/wsdl/soap/">
    <s0:types>
    <xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://saac.ssq.local/commun" xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <xs:element name="getDescripteurCourt">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="nomPhysique" type="xs:string"/>
    <xs:element name="codeValeur" type="xs:string"/>
    <xs:element name="env" type="xs:string"/>
    <xs:element name="lang" type="xs:string"/>
    <xs:element name="owner" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name="getDescripteurCourtResponse">
    <xs:complexType>
    <xs:sequence>
    <xs:element name="return" type="xs:string"/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:schema>
    </s0:types>
    <s0:message name="getDescripteurCourt">
    <s0:part element="s1:getDescripteurCourt" name="parameters"/>
    </s0:message>
    <s0:message name="getDescripteurCourtResponse">
    <s0:part element="s1:getDescripteurCourtResponse" name="parameters"/>
    </s0:message>
    <s0:portType name="communwebservices">
    <s0:operation name="getDescripteurCourt" parameterOrder="parameters">
    <s0:input message="s1:getDescripteurCourt"/>
    <s0:output message="s1:getDescripteurCourtResponse"/>
    </s0:operation>
    </s0:portType>
    <s0:binding name="communwebservicesSoapBinding" type="s1:communwebservices">
    <s2:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <s0:operation name="getDescripteurCourt">
    <s2:operation soapAction="" style="document"/>
    <s0:input>
    <s2:body parts="parameters" use="literal"/>
    </s0:input>
    <s0:output>
    <s2:body parts="parameters" use="literal"/>
    </s0:output>
    </s0:operation>
    </s0:binding>
    <s0:service name="communwebservices">
    <s0:port binding="s1:communwebservicesSoapBinding" name="communwebservices">
    <s2:address location="http://localhost:7001/commun/communwebservices"/>
    </s0:port>
    </s0:service>
    </s0:definitions>
    Can anyone help me with this? I dont understand where this exception is coming from.
    I you need more informaion, just ask I will be glad to provide you more details.
    Thank you very much
    Jean-Philippe Leblond

    webservice.operation.lastResult["return"];
    If you are doing that in a result handler, do not use
    lastResult, which is intended for binding espressions only. Use
    event.result.
    Tracy

  • 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

  • Unable to convert imported document to WSDL

    Hi all, we're excperienced with a problem during the creation of an external definition with this WSDL file:
    <?xml version="1.0" encoding="utf-8" ?>
    - <!--             Generated by WSDLDefinitionsParser   
      -->
    - <wsdl:definitions xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:ns1="urn:java/lang" xmlns:ns0="http://www.w3.org/2001/XMLSchema" xmlns:ns3="urn:java.lang" targetNamespace="urn:WSCatalogoServiceWsd/WSCatalogoServiceVi/rpc_enc" xmlns:ns2="urn:ws.catalogo.dto" xmlns:tns="urn:WSCatalogoServiceWsd/WSCatalogoServiceVi/rpc_enc">
    - <wsdl:types>
    - <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:java/lang" xmlns:tns="urn:java/lang" elementFormDefault="qualified">
    - <xs:complexType name="ArrayOfString">
    - <xs:complexContent>
    - <xs:restriction xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" base="soapenc:Array">
      <xs:attribute ref="soapenc:arrayType" wsdl:arrayType="xs:string[]" nillable="true" />
      </xs:restriction>
      </xs:complexContent>
      </xs:complexType>
      </xs:schema>
    - <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:java.lang" xmlns:tns="urn:java.lang" elementFormDefault="qualified">
    - <xs:complexType name="Exception">
    - <xs:complexContent>
    - <xs:extension base="tns:Throwable">
      <xs:sequence />
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
    - <xs:complexType name="Throwable">
    - <xs:sequence>
      <xs:element name="message" type="xs:string" nillable="true" minOccurs="0" />
      </xs:sequence>
      </xs:complexType>
      </xs:schema>
    - <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:meli.org.ngc.common.model" xmlns:tns="urn:meli.org.ngc.common.model" elementFormDefault="qualified">
    - <xs:complexType name="Titolo">
    - <xs:complexContent>
    - <xs:extension base="tns:ModelInfo">
    - <xs:sequence>
      <xs:element name="autore" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="collana" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="collana_num_interno" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="committente" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="copieGratuite" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="copieGratuiteAmmesse" type="xs:boolean" />
      <xs:element name="copieOrdinate" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="disponibilita" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="ean" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="editore" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="editoreId" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="formatoPrezzo" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="fornitureBloccate" type="xs:boolean" />
      <xs:element name="isbn" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="nota" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="pagamentoOccasionale" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="pagamentoOccasionaleGiorni" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="prezzo" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="qtaDisponibile" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="riga" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="rispostaEditore" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="rispostaEditoreDesc" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="sovraScontoOccasionale" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="statoVendita" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="statoVenditaDesc" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="tempoInserimento" type="xs:long" />
      <xs:element name="titolo" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="vendibilita" type="xs:string" nillable="true" minOccurs="0" />
      </xs:sequence>
      </xs:extension>
      </xs:complexContent>
      </xs:complexType>
    - <xs:complexType name="ModelInfo">
      <xs:sequence />
      </xs:complexType>
    - <xs:complexType name="ArrayOfTitolo">
    - <xs:complexContent>
    - <xs:restriction xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" base="soapenc:Array">
      <xs:attribute ref="soapenc:arrayType" wsdl:arrayType="tns:Titolo[]" nillable="true" />
      </xs:restriction>
      </xs:complexContent>
      </xs:complexType>
      </xs:schema>
    - <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="urn:ws.catalogo.dto" xmlns:tns="urn:ws.catalogo.dto" elementFormDefault="qualified" xmlns:s0="urn:meli.org.ngc.common.model">
      <xs:import namespace="urn:meli.org.ngc.common.model" />
    - <xs:complexType name="InfoTitoli">
    - <xs:sequence>
      <xs:element name="codErrore" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="paramErrore" type="xs:string" nillable="true" minOccurs="0" />
      <xs:element name="titoli" type="s0:ArrayOfTitolo" nillable="true" minOccurs="0" />
      </xs:sequence>
      </xs:complexType>
      </xs:schema>
      </wsdl:types>
    - <wsdl:message name="autenticaUtenteIn">
      <wsdl:part name="userName" type="ns0:string" />
      <wsdl:part name="password" type="ns0:string" />
      </wsdl:message>
    - <wsdl:message name="autenticaUtenteOut">
      <wsdl:part name="Response" type="ns0:boolean" />
      </wsdl:message>
    - <wsdl:message name="leggiTitoliDaArrayCodiciIsbnEanIn">
      <wsdl:part name="codiciIsbnEan" type="ns1:ArrayOfString" />
      <wsdl:part name="userName" type="ns0:string" />
      <wsdl:part name="password" type="ns0:string" />
      </wsdl:message>
    - <wsdl:message name="leggiTitoliDaArrayCodiciIsbnEanOut">
      <wsdl:part name="Response" type="ns2:InfoTitoli" />
      </wsdl:message>
    - <wsdl:message name="leggiTitoliDaArrayCodiciIsbnEan_java.lang.Exception">
      <wsdl:part name="leggiTitoliDaArrayCodiciIsbnEan_java.lang.Exception" type="ns3:Exception" />
      </wsdl:message>
    - <wsdl:message name="leggiTitoliDaAttachmentIsbnEanIn">
      <wsdl:part name="inputFile" type="ns0:base64Binary" />
      <wsdl:part name="userName" type="ns0:string" />
      <wsdl:part name="password" type="ns0:string" />
      </wsdl:message>
    - <wsdl:message name="leggiTitoliDaAttachmentIsbnEanOut">
      <wsdl:part name="Response" type="ns2:InfoTitoli" />
      </wsdl:message>
    - <wsdl:portType name="WSCatalogoServiceVi_Rpc_enc">
    - <wsdl:operation name="autenticaUtente">
      <wsdl:input message="tns:autenticaUtenteIn" />
      <wsdl:output message="tns:autenticaUtenteOut" />
      </wsdl:operation>
    - <wsdl:operation name="leggiTitoliDaArrayCodiciIsbnEan">
      <wsdl:input message="tns:leggiTitoliDaArrayCodiciIsbnEanIn" />
      <wsdl:output message="tns:leggiTitoliDaArrayCodiciIsbnEanOut" />
      <wsdl:fault name="java.lang.Exception" message="tns:leggiTitoliDaArrayCodiciIsbnEan_java.lang.Exception" />
      </wsdl:operation>
    - <wsdl:operation name="leggiTitoliDaAttachmentIsbnEan">
      <wsdl:input message="tns:leggiTitoliDaAttachmentIsbnEanIn" />
      <wsdl:output message="tns:leggiTitoliDaAttachmentIsbnEanOut" />
      </wsdl:operation>
      </wsdl:portType>
      </wsdl:definitions>
    The error is:
    Unable to convert imported document to WSDL
    Reason: Attribute nillable=true is not permitted at position <wsdl:definitions><wsdl:types><xs:schema><xs:complexType><xs:complexContent><xs:restriction><xs:attribute>
    Check the selected category
    Can anyone help us ?
    Thanks in advance
    Best regards
    Gianfranco Bello

    Hi Gianfranco Bello
    Can you try and remove atrribute <b>nillable</b>=true from your wsdl
    It may sound awkward but it worked for me i had a same problem with my wsdl
    Regards
    Mitesh

  • Getting Invalid WSDL error for every WSDL file

    hi
    I recently started to work on jdeveloper 10.1 3 and i am trying to develope client for google web api.
    but when i trying to create webservice using java web service form WSDL option.but when i am giving wsdl file it is giving me error like Invalid WSDL and when i click why not ? button it is saying that URL is malformed.
    here is URL
    jdev.uddi.bindingtemplate:http://uddi.xmethods.com/inquire/0B06E7E7-0F4D-BC86-4FFD-E2C8C0F43C2A
    this is generated by UDDI registrey browser by jdeveloper it self.
    this is happening with evety WSDL file. I think there is some problem with my Jdeveloper.
    Please help me.

    hi
    Could you help me on following error.
    I am trying to deploy webservice on Oracle Applicaiton server.
    But i am getting following message on Deployment message window of Jdeveloper
    ---- Deployment started. ---- Apr 27, 2006 5:40:38 PM
    Target platform is Oracle Application Server 10g 10.1.3 (KunalAppServer).
    Wrote WAR file to D:\users\kunal\sdk\oracel_ide\jdevstudio1013_JDK\jdev\mywork\WebService\heloservice\deploy\WebServices.war
    Wrote EAR file to D:\users\kunal\sdk\oracel_ide\jdevstudio1013_JDK\jdev\mywork\WebService\heloservice\deploy\WebService-heloservice-WS.ear
    Uploading file WebService-heloservice-WS.ear ...
    Application Deployer for WebService-heloservice-WS STARTS.
    Copy the archive to D:\product\10.1.3\OracleAS_1\j2ee\home\applications\WebService-heloservice-WS.ear
    Initialize D:\product\10.1.3\OracleAS_1\j2ee\home\applications\WebService-heloservice-WS.ear begins...
    Unpacking WebService-heloservice-WS.ear
    Done unpacking WebService-heloservice-WS.ear
    Unpacking WebServices.war
    Done unpacking WebServices.war
    Initialize D:\product\10.1.3\OracleAS_1\j2ee\home\applications\WebService-heloservice-WS.ear ends...
    Starting application : WebService-heloservice-WS
    Initializing ClassLoader(s)
    Initializing EJB container
    Loading connector(s)
    Starting up resource adapters
    Initializing EJB sessions
    Committing ClassLoader(s)
    Initialize WebServices begins...
    Initialize WebServices ends...
    Started application : WebService-heloservice-WS
    Binding web application(s) to site default-web-site begins...
    Binding WebServices web-module for application WebService-heloservice-WS to site default-web-site under context root WebService-heloservice-context-root
    Operation failed with error:
    org.apache.xerces.dom.DeferredElementNSImpl
    Deployment failed
    Elapsed time for deployment: 1 minute, 8 seconds
    #### Deployment incomplete. #### Apr 27, 2006 5:41:47 PM

  • Handling xsd:import in XSLT

    I'm trying to generate an input form from an XML schema using XSL.
    Unfortunatly, the schema is spread out over several files and uses xsd:import to piece the whole thing together. So, when I try to parse it, all I get is the elements declared in the first file, and none of the includes.
    How can I get around that?
    The file looks like:
    <?xml version="1.0" encoding="utf-8"?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
       <xs:include schemaLocation="restOfSchema.xsd"/>
       <xs:element ref="rootElement"/>
    </xs:schema>And I get:
    <html>
    <body>
       <form method="post" action="next.html">
         <h1>rootElement:</h1>
         <p></p>
       </form>
    </body>
    </html>There should be several sub elements and such, but as you can see, they don't make it.

    Compared to what alternative?That was part of my question :)
    I hope there is one because now I'm getting stack overflow errors when I try to transform my latest stylesheet.
    I was trying to solve an issue with this little bit of code:
    <xsl:for-each select="//xsd:include[$count]">$count is a template parameter. I have to call the template recursively because looping results in too many templates being applied.
    The problem (I think) is that it only selects includes in the document I've selected searching for element definitions (which gets opened because my root document has many includes and references to elements in those documents) so, I have to use select="document($doc)/xsd:schema/... where $doc is a reference to a value picked from the schemaLocation attribute of an include.
    So what is happening (I think) is that while I'm still in the document I had selected to search for definitions (and found them), //xsd:include only matches nodes in that document. So I tried this to search for includes:
    <xsl:for-each select="document($root)/xsd:schema/xsd:include[$count]"> so that I could go back and select those include nodes from the root document (fortunately they aren�t anywhere else). Unfortunately, that gets me a stack overflow.

  • Problem while import

    hi experts,
    i am facing the problem while importing DC. here is the msg i am getting .
    Problems were encountered during import: 
    Failed to read the project description file (.project) for LocalDevelopmentpapermtcs.com.  The file has been changed on disk, and it now contains invalid information.  The project will not function properly until the description file is restored to a valid state.
    can anybody help me on this issue.
    thank you ,
    vijai

    hi Sumit ,
    how do i resync the dc.
    can u help me step by step.
    vijai

Maybe you are looking for