WSDL/XSD problem

I deployed one pl/sql web services using jdeveloper10g to oc4j. within this webservices, there are two operations which reture two set of xml data.
For each operation call, the biztalk server need to validate against xsd files that we provide to them.
Here are the problems:
1. The xsd was generated from database. but in the soap body, there are two extra tags being added by (see below)
<env:Body>
<ns0:getSuppliersCsResponseElement>
<ns0:pdatasetOut><SUPPLIERS><SUPPLIER><SUPPLIER_ID>6144</SUPPLIER_ID><SUPPLIER_NAME>Botanica</SUPPLIER_NAME>
<SUPPLIER_LAST_MODIFIED>2006-01-22</SUPPLIER_LAST_MODIFIED><JI_OWNED>1</JI_OWNED><BRANDS_EXCLUSIVE_TO_JI></BRANDS_EXCLUSIVE_TO_JI><LIBRARIES><LIBRARY><LIBRARY_ID>5514</LIBRARY_ID><LIBRARY_NAME>Botanica</LIBRARY_NAME><LIBRARY_TYPE>Rights Managed</LIBRARY_TYPE><LIBRARY_LAST_MODIFIED>2005-09-01</LIBRARY_LAST_MODIFIED><RESTRICTIONS><WEBSITE><WEBSITE_ID>2</WEBSITE_ID><WEBSITE_NAME>PictureQuest</WEBSITE_NAME><COUNTRY_CODES><ISO3>ABW</ISO3><ISO3>AND</ISO3></COUNTRY_CODES></WEBSITE></RESTRICTIONS></LIBRARY></LIBRARIES></SUPPLIER></SUPPLIERS></ns0:pdatasetOut>
</ns0:getSuppliersCsResponseElement>
</env:Body>
there two <ns0:getSuppliersCsResponseElement> and <ns0:pdatasetOut> are not in my original xsd file. so biztalk returned failure when it validate message body. Shall I change me xsd to add these two or there is anyway doing this?
2. I have two operations with different xsd files. How to attach correct or both xsd files within the soap message? or can i do something with WSDL file to inclulde two schemalocations?
3. the soap body can be over 100MB big. How to streaming the message?

The following is the WSDL file generated by Jdeveloper
<definitions
name="tt"
targetNamespace="http://webdevdb/Tt.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://webdevdb/Tt.wsdl"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
>
<types>
<schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://webdevdb/Tt.wsdl"
elementFormDefault="qualified" xmlns:tns="http://webdevdb/Tt.wsdl" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soap12-enc="http://www.w3.org/2003/05/soap-encoding">
<element name="getRfitemsCsElement" type="decimal" nillable="true"/>
<element name="getRfitemsCsResponseElement" type="tns:TtUser_getRfitemsCs_Out" nillable="true"/>
<complexType name="TtUser_getRfitemsCs_Out">
<sequence>
<element name="pdatasetOut" type="string" nillable="true"/>
</sequence>
</complexType>
<element name="getSuppliersCsElement" type="string" nillable="true"/>
<element name="getSuppliersCsResponseElement" type="tns:TtUser_getSuppliersCs_Out"
nillable="true"/>
<complexType name="TtUser_getSuppliersCs_Out">
<sequence>
<element name="pdatasetOut" type="string" nillable="true"/>
</sequence>
</complexType>
</schema>
</types>
<message name="Tt_getRfitemsCs">
<part name="parameters" element="tns:getRfitemsCsElement"/>
</message>
<message name="Tt_getRfitemsCsResponse">
<part name="result" element="tns:getRfitemsCsResponseElement"/>
</message>
<message name="Tt_getSuppliersCs">
<part name="parameters" element="tns:getSuppliersCsElement"/>
</message>
<message name="Tt_getSuppliersCsResponse">
<part name="result" element="tns:getSuppliersCsResponseElement"/>
</message>
<portType name="tt">
<operation name="getRfitemsCs">
<input message="tns:Tt_getRfitemsCs"/>
<output message="tns:Tt_getRfitemsCsResponse"/>
</operation>
<operation name="getSuppliersCs">
<input message="tns:Tt_getSuppliersCs"/>
<output message="tns:Tt_getSuppliersCsResponse"/>
</operation>
</portType>
<binding name="ttSoap12Http" type="tns:tt">
<soap12:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="getRfitemsCs">
<soap12:operation soapAction="http://webdevdb/Tt.wsdl/getRfitemsCs" soapActionRequired="false"/>
<input>
<soap12:body use="literal"/>
</input>
<output>
<soap12:body use="literal" parts="result"/>
</output>
</operation>
<operation name="getSuppliersCs">
<soap12:operation soapAction="http://webdevdb/Tt.wsdl/getSuppliersCs" soapActionRequired="false"/>
<input>
<soap12:body use="literal"/>
</input>
<output>
<soap12:body use="literal" parts="result"/>
</output>
</operation>
</binding>
<service name="tt">
<port name="ttSoap12HttpPort" binding="tns:ttSoap12Http">
<soap12:address location="http://192.168.10.151:8888/Application2-proj1-context-root/ttSoap12HttpPort"/>
</port>
</service>
</definitions>

Similar Messages

  • Wsdl,xsd,xls

    am new to wsdl,xsd,xls. i read all these 3 topics. but still can anyone tell me what is it used for in layman terms.
    a.are these kind of contracts which should be satisfied while message is sent from ep1 to ep2?
    b.are these 3 files generated using automated tool or we have to write it from scratch
    c.for example if i am going to send one xml file as message from ep1 to ep2, how many wsdl,xsd and xsl files required.thanks

    a.are these kind of contracts which should be satisfied while message is sent from ep1 to ep2? You claimed to have read about all three. It doesn't seem so.
    WSDL defines the service, XSD defines the format of the XML file. And XSL (not XLS) is used for example to modify XML via XSLT.
    b.are these 3 files generated using automated tool or we have to write it from scratch There are automated tools of course, writing them by hand would be very time consuming.
    c.for example if i am going to send one xml file as message from ep1 to ep2, how many wsdl,xsd and xsl files required.thanksI think you have some more reading to do. You can send an XML file without using any of those. However, if you're talking about webservices, then WSDL and XSD become involved.
    I suggest you hit the books again.

  • Help needed with wsdl compilation problem

    Hi all,
    I am trying to perform a wsdl2java run on a wsdl, but it keeps failing and I can't work out why.
    Can anyone help me spot the problem?
    Here is the problem I get:
    [WARN] Type {http://Input.LeaseBaseGetMntcHistory.remarketing.gf.com}MntcHistory missing!
    [WARN] Type {http://Output.LeaseBaseGetMntcHistory.remarketing.gf.com}MaintenanceHistory missing!And here is the full wsdl
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions xmlns:tns="http://Master.LeaseBaseGetMntcHistory.Remarketing.gf.com" xmlns:ns0="http://Input.LeaseBaseGetMntcHistory.remarketing.gf.com" xmlns:ns1="http://Output.LeaseBaseGetMntcHistory.remarketing.gf.com" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" name="LeaseBaseMntcHistory" targetNamespace="http://Master.LeaseBaseGetMntcHistory.Remarketing.gf.com">
        <wsdl:types>
         <xsd:schema xmlns = "http://Input.LeaseBaseGetMntcHistory.remarketing.gf.com"
               targetNamespace = "http://Input.LeaseBaseGetMntcHistory.remarketing.gf.com"
               xmlns:xsd="http://www.w3.org/2001/XMLSchema"
               elementFormDefault="unqualified"
               attributeFormDefault="unqualified">
              <xsd:element name="FleetID" type="xsd:string"/>
              <xsd:element name="CountryID" type="xsd:string"/>
              <xsd:element name="RegID" type="xsd:string"/>
              <xsd:element name="CompanyID" type="xsd:string"/>
              <xsd:element name="ChassisID" type="xsd:string"/>
              <xsd:element name="FleetDetails">
                   <xsd:complexType>
                        <xsd:sequence>
                             <xsd:element ref="FleetID"/>
                             <xsd:element ref="CountryID"/>
                             <xsd:element ref="RegID" minOccurs="0"/>
                             <xsd:element ref="CompanyID" minOccurs="0"/>
                             <xsd:element ref="ChassisID"/>
                        </xsd:sequence>
                   </xsd:complexType>
              </xsd:element>
              <xsd:element name="MntcHistory">
                   <xsd:complexType>
                        <xsd:sequence>
                             <xsd:element ref="FleetDetails"/>
                        </xsd:sequence>
                   </xsd:complexType>
              </xsd:element>
         </xsd:schema>
         <xsd:schema xmlns = "http://Output.LeaseBaseGetMntcHistory.remarketing.gf.com"
               targetNamespace = "http://Output.LeaseBaseGetMntcHistory.remarketing.gf.com"
               xmlns:xsd="http://www.w3.org/2001/XMLSchema"
               elementFormDefault="qualified"
               attributeFormDefault="unqualified">
              <xsd:element name="Date" type="xsd:string"/>
              <xsd:element name="Mileage" type="xsd:string"/>
              <xsd:element name="StatusCD" type="xsd:string"/>
              <xsd:element name="Operation" type="xsd:string"/>
              <xsd:element name="Details">
                   <xsd:complexType>
                        <xsd:sequence>
                             <xsd:element ref="Detail" maxOccurs="unbounded"/>
                        </xsd:sequence>
                   </xsd:complexType>
              </xsd:element>
              <xsd:element name="FleetID" type="xsd:string"/>
              <xsd:element name="RegID" type="xsd:string"/>
              <xsd:element name="MaintenanceHistory">
                   <xsd:complexType>
                        <xsd:sequence>
                             <xsd:element ref="FleetID"/>
                             <xsd:element ref="RegID"/>
                             <xsd:element ref="LstUpdateDate"/>
                             <xsd:element ref="MntcWorkHistory"/>
                        </xsd:sequence>
                   </xsd:complexType>
              </xsd:element>
              <xsd:element name="LstUpdateDate" type="xsd:string"/>
              <xsd:element name="MntcWorkHistory">
                   <xsd:complexType>
                        <xsd:sequence>
                             <xsd:element ref="MntcWork" maxOccurs="unbounded"/>
                        </xsd:sequence>
                   </xsd:complexType>
              </xsd:element>
              <xsd:element name="MntcWork">
                   <xsd:complexType>
                        <xsd:sequence>
                             <xsd:element ref="Date"/>
                             <xsd:element ref="Mileage"/>
                             <xsd:element ref="StatusCD"/>
                             <xsd:element ref="LineItems"/>
                        </xsd:sequence>
                   </xsd:complexType>
              </xsd:element>
              <xsd:element name="LineItems">
                   <xsd:complexType>
                        <xsd:sequence>
                             <xsd:element ref="LineItem" maxOccurs="unbounded"/>
                        </xsd:sequence>
                   </xsd:complexType>
              </xsd:element>
              <xsd:element name="LineItem">
                   <xsd:complexType>
                        <xsd:sequence>
                             <xsd:element ref="Operation"/>
                             <xsd:element ref="Details"/>
                        </xsd:sequence>
                   </xsd:complexType>
              </xsd:element>
              <xsd:element name="Detail" type="xsd:string"/>
         </xsd:schema>
        </wsdl:types>
        <wsdl:message name="MntcHistory">
            <wsdl:part name="parameters" type="ns0:MntcHistory"/>
        </wsdl:message>
        <wsdl:message name="MaintenanceHistory">
            <wsdl:part name="parameters" type="ns1:MaintenanceHistory"/>
        </wsdl:message>
        <wsdl:portType name="portType">
            <wsdl:operation name="LeaseBaseClientOp">
                <wsdl:input message="tns:MntcHistory"/>
                <wsdl:output message="tns:MaintenanceHistory"/>
            </wsdl:operation>
        </wsdl:portType>
        <wsdl:binding name="intfwsLeaseBaseClientEndpoint0Binding" type="tns:portType">
            <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
            <wsdl:operation name="LeaseBaseClientOp">
                <soap:operation style="rpc" soapAction="/Processes/LeaseBaseClientOp"/>
                <wsdl:input>
                    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://Input.LeaseBaseGetMntcHistory.remarketing.gf.com" parts="parameters"/>
                </wsdl:input>
                <wsdl:output>
                    <soap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="http://Output.LeaseBaseGetMntcHistory.remarketing.gf.com" parts="parameters"/>
                </wsdl:output>
            </wsdl:operation>
        </wsdl:binding>
        <wsdl:service name="intfLeaseBaseClient-service">
            <wsdl:port name="intfwsLeaseBaseClientEndpoint0" binding="tns:intfwsLeaseBaseClientEndpoint0Binding">
                <soap:address location="http://localhost:8080/Processes/intfwsLeaseBaseClientEndpoint0"/>
            </wsdl:port>
        </wsdl:service>
    </wsdl:definitions>Thanks in advance!

    Hello
    You may try something like the modified code below.
    Noticiable changes :
    #1 - Removed the parentheses. Your original code won't yield alias list but a list of finder objects, which is the reason why Preview opens the image. (The statment 'open finderObject' behaves the same as double clicking it in Finder)
    #2 - Only delete the original jpeg files which are converted to tiff.
    #3 - Build new path for converted image.
    #4 - Save in new path. (When saving image in a format other than its original format, always save the image to a new file and do not attempt to overwrite the source file.)
    cf.
    http://www.macosxautomation.com/applescript/imageevents/08.html
    on run
    tell application "Finder"
    set PicturesFolder to (path to home folder as string) & "Pictures:SenseCam:" as alias
    set Photographs to get entire contents of PicturesFolder as alias list -- #1
    end tell
    set DonePhotos to {} -- #2
    tell application "Image Events"
    launch
    repeat with Photo in Photographs
    set Photo to Photo's contents
    set oldPath to Photo as string
    if oldPath ends with ".jpg" then
    set newPath to oldPath's text 1 thru -5 & ".tif" -- #3
    set ImageRef to open Photo
    save ImageRef as TIFF in newPath -- #4
    close ImageRef
    set end of DonePhotos to Photo -- #2
    end if
    end repeat
    end tell
    tell application "Finder"
    delete DonePhotos -- #2
    end tell
    end run
    Hope this may help,
    H

  • WSDL validation problem with WS-I

    I created a WSDL with jDeveloper 10.1.3.2 following the Oracle Tutorial
    http://www.oracle.com/technology/obe/obe1013jdev/wstopdown/wstopdown.htm
    At the point where i have to validate the WSDL with the WS-I tester i get an error message:
    Assertion: BP2701
    The wsdl:definitions namespace is not: http://schemas.xmlsoap.org/wsdl/
    All the entrys inside teh WSDL are written from jdeveloper.
    the output WSDL looks like:
    <definitions targetNamespace="urn:CreditRating"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:tns="urn:CreditRating"
    xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
    xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:types="http://CreditRating.xsd">
    <types>
    <schema targetNamespace="http://CreditRating.xsd"
    xmlns="http://www.w3.org/2001/XMLSchema"
    xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
    <element name="ssn" type="string"/>
    <element name="rating" type="int"/>
    <element name="error" type="string"/>
    </schema>
    </types>
    <message name="CreditRatingRequestMessage">
    <part name="ssn" element="types:ssn"/>
    </message>
    <message name="CreditRatingResponseMessage">
    <part name="rating" element="types:rating"/>
    </message>
    <message name="CreditRatingFaultMessage">
    <part name="error" element="types:error"/>
    </message>
    <portType name="CreditRating">
    <operation name="processCreditRating">
    <input message="tns:CreditRatingRequestMessage"/>
    <output message="tns:CreditRatingRequestMessage"/>
    <fault message="tns:CreditRatingFaultMessage" name="negativCredit"/>
    </operation>
    </portType>
    <binding name="CreditRatingSoapHttp" type="tns:CreditRating">
    <soap:binding style="document"
    transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="processCreditRating">
    <soap:operation soapAction="urn:CreditRating/processCreditRating"/>
    <input>
    <soap:body use="literal" parts="ssn"/>
    </input>
    <output>
    <soap:body use="literal" parts="ssn"/>
    </output>
    <fault name="negativCredit">
    <soap:fault use="literal" name="negativCredit"/>
    </fault>
    </operation>
    </binding>
    <service name="CreditRatingService">
    <port name="CreditRatingServiceSoapHttpPort"
    binding="tns:CreditRatingSoapHttp">
    <soap:address location="tbd"/>
    </port>
    </service>
    </definitions>
    I can not see where the porblem is. Can someone help me please?
    Tanks Bs

    Hi ,
    there is not any problem in code or in function.
    You just need to double click on Excel field where you are having that problem of ####.
    Whenever display size of cell is less then the data size then it's showing as ###. so you just need to double click on it and make it as per data length...
    -Maharshi

  • Portal Service from wsdl testing problem

    Hi all,I use Developer Studio to generate sap portal wsdl client,when I finished generating,I want to do test.But it throws the Exception like that
    java.lang.IllegalStateException: Not able to initialize Web Service configuration for service TPOStatusService#
    com.sapportals.portal.prt.service.soap.mapping.SpecializedRegistry.initSerializersXML(SpecializedRegistry.java:601)
    com.sapportals.portal.prt.service.soap.mapping.SpecializedRegistry.initXMLBased(SpecializedRegistry.java:477)
    com.sapportals.portal.prt.service.soap.SOAPServiceManager.getSpecializedRegistry(SOAPServiceManager.java:321)
    com.sapportals.portal.prt.service.soap.PRTSOAPCall.invokeMethod(PRTSOAPCall.java:181)
    com.ilog.pct.tpo.proxy.TPOService.getProblemInfo(TPOService.java:168     at com.ilog.pct.tpo.pages.KpiPage$KpiPageDynPage.doProcessAfterInput(KpiPage.java:48)
    I don't know what's the problem.Can anyone help me to solve this problem?
    The followings is my wsdl:
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions targetNamespace="http://ws.tpo.ilog.com" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="http://ws.tpo.ilog.com" xmlns:intf="http://ws.tpo.ilog.com" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <!--WSDL created by Apache Axis version: 1.3
    Built on Oct 05, 2005 (05:23:37 EDT)-->
    <wsdl:types>
      <schema elementFormDefault="qualified" targetNamespace="http://ws.tpo.ilog.com" xmlns="http://www.w3.org/2001/XMLSchema">
       <element name="getProblemInfo">
        <complexType>
         <sequence>
          <element name="name" type="xsd:string"/>
         </sequence>
        </complexType>
       </element>
       <element name="getProblemInfoResponse">
        <complexType>
         <sequence>
          <element name="getProblemInfoReturn" type="impl:ProblemInfo"/>
         </sequence>
        </complexType>
       </element>
       <simpleType name="ProcessStatus">
        <restriction base="xsd:string">
         <enumeration value="1"/>
         <enumeration value="2"/>
         <enumeration value="3"/>
        </restriction>
       </simpleType>
       <complexType name="Vehicle">
        <sequence>
         <element name="cost" type="xsd:double"/>
         <element name="count" type="xsd:int"/>
         <element name="fixcost" type="xsd:double"/>
         <element name="name" nillable="true" type="xsd:string"/>
        </sequence>
       </complexType>
       <complexType name="ArrayOfVehicle">
        <sequence>
         <element maxOccurs="unbounded" minOccurs="0" name="item" type="impl:Vehicle"/>
        </sequence>
       </complexType>
       <complexType name="ProblemInfo">
        <sequence>
         <element name="numbervehicles" type="xsd:int"/>
         <element name="numbervisit" type="xsd:int"/>
         <element name="processStatus" nillable="true" type="impl:ProcessStatus"/>
         <element name="shipvisit" type="xsd:int"/>
         <element name="total" type="xsd:double"/>
         <element name="vehicle" nillable="true" type="impl:ArrayOfVehicle"/>
        </sequence>
       </complexType>
       <complexType name="SvcException">
        <sequence>
         <element name="errorMsg" nillable="true" type="xsd:string"/>
        </sequence>
       </complexType>
       <element name="fault" type="impl:SvcException"/>
      </schema>
    </wsdl:types>
       <wsdl:message name="getProblemInfoResponse">
          <wsdl:part element="impl:getProblemInfoResponse" name="parameters"/>
       </wsdl:message>
       <wsdl:message name="getProblemInfoRequest">
          <wsdl:part element="impl:getProblemInfo" name="parameters"/>
       </wsdl:message>
       <wsdl:message name="SvcException">
          <wsdl:part element="impl:fault" name="fault"/>
       </wsdl:message>
       <wsdl:portType name="TPOProcessSvc">
          <wsdl:operation name="getProblemInfo">
             <wsdl:input message="impl:getProblemInfoRequest" name="getProblemInfoRequest"/>
             <wsdl:output message="impl:getProblemInfoResponse" name="getProblemInfoResponse"/>
             <wsdl:fault message="impl:SvcException" name="SvcException"/>
          </wsdl:operation>
       </wsdl:portType>
       <wsdl:binding name="TPOProcessSvcSoapBinding" type="impl:TPOProcessSvc">
          <wsdlsoap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
          <wsdl:operation name="getProblemInfo">
             <wsdlsoap:operation soapAction=""/>
             <wsdl:input name="getProblemInfoRequest">
                <wsdlsoap:body use="literal"/>
             </wsdl:input>
             <wsdl:output name="getProblemInfoResponse">
                <wsdlsoap:body use="literal"/>
             </wsdl:output>
             <wsdl:fault name="SvcException">
                <wsdlsoap:fault name="SvcException" use="literal"/>
             </wsdl:fault>
          </wsdl:operation>
       </wsdl:binding>
       <wsdl:service name="TPOProcessSvcService">
          <wsdl:port binding="impl:TPOProcessSvcSoapBinding" name="TPOProcessSvc">
             <wsdlsoap:address location="http://localhost:8080/tpo-web/services/TPOProcessSvc"/>
          </wsdl:port>
       </wsdl:service>
    </wsdl:definitions>

    Your installation for SAP JCO is not correct. Download the SAP JCO from service.sap.com and install it on your computer as the installation guide says.
       The above error is due to missing file librfc32.dll. If you are using windows operating system. Put the dll files in windows/system32 directory. thank you.
    Read the following thread. this should definitely solve your problem.
    https://forums.sdn.sap.com/profile.jspa?userID=608260
    PS: reward points if this hepls. thank you
    Message was edited by: Prakash  Singh

  • WSDL - Java problem

    Hi all,
    I have been trying to generate a web service from a WSDL file (which, in my opinion, is the best way to create a web service when you don't already have a program). But there's some problems I run across which I can't seem to find the solution for.
    My traject should be: WSDL -> Java Files -> Compiling -> Deployment, where my primary WSDL should not be changed (or just endpoint address)
    I use JWSDP 1.2.
    1)
    When I try to replicate the helloservice, static stub example with my own WSDL file, I receive the following error:
    wscompile.bat -gen:server -d build -classpath build config-wsdl.xml
    error: generator error: no encoder for type "{http://www.w3.org/2001/XMLSchema}date" and Java type "java.util.Calendar"
    can anyone explain what this is?
    2)
    I tried -import and -keep instead of -gen:server, to get my Java files. This worked and created a lot of java files and even an implementation file, where I could create my webservice. So far it looked good, but after compiling and deploying, the service does not work. The problem is that the generated classes all have changed names (first letter lowercase, instead of uppercase), resulting in a non-working application.
    SEVERE: Exception sending context initialized event to listener instance of class com.sun.xml.rpc.server.http.JAXRPCContextListener
    java.lang.NoClassDefFoundError: MyService/MyProtocol_myOperation_ResponseStruct
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:217)
    at com.sun.xml.rpc.server.http.JAXRPCRuntimeInfoParser.loadClass(JAXRPCRuntimeInfoParser.java:150)
    Where myOperation in my WSDL file is called 'MyOperation'
    So now I'm stuck, can anybody help me or give me a step-by-step how to create a service

    Here's how I do it. I hope this won't annoy other people since this will be a long code post.
    1) Create the java interface: DateServiceInf.java:
    package MyService;
    import MyService.holders.*;
    public interface DateServiceInf extends java.rmi.Remote {
         public void setDate(java.util.Date date) throws java.rmi.RemoteException;
         public void getDate(DateHolder dholder) throws java.rmi.RemoteException;
    2) Create the java implementation: DateServiceImpl.java:
    package MyService;
    public class DateServiceImpl implements MyService.DateServiceInf{
         java.util.Date date = new java.util.Date();     //current date
         public DateServiceImpl() {
         public void getDate(MyService.holders.DateHolder dholder) throws java.rmi.RemoteException{
              dholder.setDate(date);
         public void setDate(java.util.Date date) throws java.rmi.RemoteException{
              this.date = date;
    3) Create the holder class: DateHolder.java
    package MyService.holders;
    public class DateHolder {
         private java.util.Date date;
         public DateHolder() {
              date = null;
         public java.util.Date getDate() {
              return date;
         public void setDate(java.util.Date date) {
              this.date = date;
    Compile the whole thing now.
    (you can skip to step 5 below)
    4) Using Apache axis to generate the wsdl file, assume the unzip axis1.1 is located at d:\axis-1_1 (windows bat file) and jdk at c:\j2sdk1.4.0: (make sure all files above are located in the proper directories (packages).
    @echo off
    set AXIS_HOME=d:\axis-1_1
    set AXIS_LIB=%AXIS_HOME%\lib
    set AXISCLASSPATH=%AXIS_LIB%\axis.jar;%AXIS_LIB%\commons-discovery.jar;%AXIS_LIB%\commons-logging.jar;%AXIS_LIB%\jaxrpc.jar;%AXIS_LIB%\saaj.jar;%AXIS_LIB%\log4j-1.2.8.jar;%AXIS_LIB%\xml-apis.jar;%AXIS_LIB%\xercesImpl.jar;%AXIS_LIB%\wsdl4j.jar
    c:\j2sdk1.4.0\bin\java -cp %AXISCLASSPATH%;. org.apache.axis.wsdl.Java2WSDL -l"http://www.mycomp.com/MyService" -n "urn:MyService" -p"MyService" "urn:MyService" -o MyService.wsdl MyService.DateServiceInf
    Here is the generated file using axis:
    <wsdl:definitions targetNamespace="urn:MyService" xmlns:impl="urn:MyService" xmlns:intf="urn:MyService"
    xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns2="http://holders.MyService"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns="http://schemas.xmlsoap.org/wsdl/">
    <wsdl:types>
    <schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://holders.MyService">
    <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
    <complexType name="DateHolder">
    <sequence>
    <element name="date" nillable="true" type="xsd:dateTime"/>
    </sequence>
    </complexType>
    </schema>
    </wsdl:types>
    <wsdl:message name="setDateResponse">
    </wsdl:message>
    <wsdl:message name="getDateResponse">
    </wsdl:message>
    <wsdl:message name="setDateRequest">
    <wsdl:part name="in0" type="xsd:dateTime"/>
    </wsdl:message>
    <wsdl:message name="getDateRequest">
    <wsdl:part name="in0" type="tns2:DateHolder"/>
    </wsdl:message>
    <wsdl:portType name="DateServiceInf">
    <wsdl:operation name="getDate" parameterOrder="in0">
    <wsdl:input name="getDateRequest" message="impl:getDateRequest"/>
    <wsdl:output name="getDateResponse" message="impl:getDateResponse"/>
    </wsdl:operation>
    <wsdl:operation name="setDate" parameterOrder="in0">
    <wsdl:input name="setDateRequest" message="impl:setDateRequest"/>
    <wsdl:output name="setDateResponse" message="impl:setDateResponse"/>
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="MyServiceSoapBinding" type="impl:DateServiceInf">
    <wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="getDate">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="getDateRequest">
    <wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:MyService"/>
    </wsdl:input>
    <wsdl:output name="getDateResponse">
    <wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:MyService"/>
    </wsdl:output>
    </wsdl:operation>
    <wsdl:operation name="setDate">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="setDateRequest">
    <wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:MyService"/>
    </wsdl:input>
    <wsdl:output name="setDateResponse">
    <wsdlsoap:body use="encoded" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:MyService"/>
    </wsdl:output>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="DateServiceInfService">
    <wsdl:port name="MyService" binding="impl:MyServiceSoapBinding">
    <wsdlsoap:address location="http://www.mycomp.com/MyService"/>
    </wsdl:port>
    </wsdl:service>
    </wsdl:definitions>
    5) Generate the wsdl using the Sun's implementation. Assume that the installation is located at: C:\j2sdkee1.4
    @echo off
    c:\j2sdk1.4.0\bin\java -cp . org.apache.axis.wsdl.Java2WSDL -l"http://www.mycomp.com/MyService" -n "urn:MyService" -p"MyService" "urn:MyService" -o MyService.wsdl MyService.DateServiceInf
    (those are 2 lines: echo and java)
    You may get a warning here.
    Here is the generated file from Sun:
    xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:ns2="http://www.mycomp.com/types" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
    <types>
    <schema targetNamespace="http://www.mycomp.com/types" xmlns:tns="http://www.mycomp.com/types" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:soap-enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns="http://www.w3.org/2001/XMLSchema">
    <import namespace="http://schemas.xmlsoap.org/soap/encoding/"/>
    <complexType name="DateHolder">
    <sequence>
    <element name="date" type="dateTime"/></sequence></complexType></schema></types>
    <message name="DateServiceInf_getDate">
    <part name="DateHolder_1" type="ns2:DateHolder"/></message>
    <message name="DateServiceInf_getDateResponse"/>
    <message name="DateServiceInf_setDate">
    <part name="Date_1" type="xsd:dateTime"/></message>
    <message name="DateServiceInf_setDateResponse"/>
    <portType name="DateServiceInf">
    <operation name="getDate" parameterOrder="DateHolder_1">
    <input message="tns:DateServiceInf_getDate"/>
    <output message="tns:DateServiceInf_getDateResponse"/></operation>
    <operation name="setDate" parameterOrder="Date_1">
    <input message="tns:DateServiceInf_setDate"/>
    <output message="tns:DateServiceInf_setDateResponse"/></operation></portType>
    <binding name="DateServiceInfBinding" type="tns:DateServiceInf">
    <operation name="getDate">
    <input>
    <soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://www.mycomp.com/wsdl"/></input>
    <output>
    <soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://www.mycomp.com/wsdl"/></output>
    <soap:operation soapAction=""/></operation>
    <operation name="setDate">
    <input>
    <soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://www.mycomp.com/wsdl"/></input>
    <output>
    <soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://www.mycomp.com/wsdl"/></output>
    <soap:operation soapAction=""/></operation>
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/></binding>
    <service name="DateService">
    <port name="DateServiceInfPort" binding="tns:DateServiceInfBinding">
    <soap:address location="REPLACE_WITH_ACTUAL_URL"/></port></service></definitions>

  • XSLT Mapper - Transform - Error when using remote WSDL/XSD

    Whenever I attempt to use JDeveloper built in XSLT Mapper on a remote WSDL service the mapper either gives me a blank mapper screen or throws a error.
    But when I pull the WSDLS and the XSDs into JDeveloper and use those for my Partner links the mapper does not have any issues.
    The WSDLS and XSDs are being generated by Weblogic 10.3 and the SOA version I'm using is 11g. Everything is the newest download of 11g as of about 3 days ago.
    Is there a known issue with the XSLT mapper or am I doing something wrong?
    If you need any other information just ask thank you.

    The XSLT service is configurable.
    http://help.adobe.com/en_US/LiveCycle/9.5/WorkbenchHelp/WS92d06802c76abadb-1cc35bda128261a 20dd-6750.html
    1) Stop LiveCycle.
    2) Add the .jars of your XSLT processor of choice to the LiveCycle server lib folder.
    3) Restart LiveCycle.
    4) Go to Workbench and stop the XSLT service. Right-click on XSLTService:1.0 and Edit Service Configuration.
    5) Enter the factory name for the given XSLT processor. I think for Xalan 2.7.1 it is org.apache.xalan.processor.TransformerFactoryImpl (but I could be wrong).
    6) Restart the service.
    Steve

  • WSDL Policy Problem

    Hi All
    I'm  facing this issue...
    My Process Integration version is: 7.1 EHP1
    When create a WSDL, this comes with the WS_POLICY by default in true!
    and thats my problem....
    I'll try to explain all my Steps:
    1.- in the ESR I Have created all the necesary (DT, MT, SI, MM, OP)
    2.- in te Directory, i Have created all objects: Receiver, Sender, I.Det, R.Det.
    3.- Right click on Sender Agreement -> Display WSDL
    4.- this windows comes with 2 things: 1 the WSDL URL and 2, the WSDL per se
    if I download the WSDL, I can change manually  the ws_policy from "true" to "standard" or "false", and with this it works fine... but this solutions doesn't works for me... I need to use the WSDL URL (http://XXXXX:50100/dir/wsdl?p=sa/10eee4f1d18632f182bf5eb4b42cfcdb)
    but, if I use, the WSDL URL, the definition inside it comes with ws_policy = TRUE and I can't change it.
    I have followed this link: /people/holger.stumm2/blog/2010/03/19/wsdl-wspolicy--what-is-it-und-how-can-i-get-rid-of-it-in-pi
    wich talks about how to replace the call of WS_POLICY with STANDARD,
    this is my real URL:
    http://XXXXX:8000/sap/bc/srt/wsdl/sdef_ZSI_LABORATORIO_GS02_REQUEST_S/wsdl11/ws_policy/document?sap-client=100
    this is my URL changed.
    http://XXXXX:8000/sap/bc/srt/wsdl/sdef_ZSI_LABORATORIO_GS02_REQUEST_S/wsdl11/STANDARD/document?sap-client=100
    but I see than this is pointing to SAP ECC and not to PI... here I'm confused.
    if this works I could see the messages from Legacy to PI in the SXI_MONITOR???
    basically what I can see with this is: a direct call to the "service interface" wich I have activated in the SPROXY.
    But I think than the Policy status can't be changed in PI...
    when I look in the Service Interface WSDL TAB I can see, than already it has the policy in true, I have set the Security profile to "NO" but the WSDL TAB shows: <wsp:UsingPolicy wsdl:required="true" />
    if someone knows how to fix it I'll apreciate it
    Thanks and Regards

    Hello,
    I know it's an old topic, but we've got the exact same problem here.
    We want to remove the policy tags in the WSDL generated by PI (7.11), or at least set  <wsp:UsingPolicy wsdl:required="false" />
    Our webservice is consumed by another application that stumbles upon these tags. Now, everytime we have to remove these tags manually. Hope someone can provide me with a solution. Thanks in advance.
    Regards,
    Floris

  • Importing xsd problems

    I'm  using two xsd.
    The first one is like  a dictionory the second one form specific.
    In the form specific xsd  I use restriction from the dictionary
    for eg: dictionary.xsd is like this
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
    xmlns="http://www.example.org/Base"
    targetNamespace="http://www.example.org/Base"
    elementFormDefault="unqualified">
    <xs:element name="A" type="AType" />
    <xs:complexType name="AType">
    <xs:sequence>
    <xs:element name="title" type="xs:string" />
    <xs:element name="name" type="xs:string" minOccurs="0" />
    </xs:sequence>
    </xs:complexType>
    </xs:schema>
    form.xsd is
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
    xmlns="http://www.example.org/Restriction"
    targetNamespace="http://www.example.org/Restriction"
    xmlns:base="http://www.example.org/Base"
    elementFormDefault="unqualified">
    <xs:import namespace="http://www.example.org/Base"
    schemaLocation="dictionary.xsd" />
    <xs:element name="ARestricted" type="ARestrictedType" />
    <xs:complexType name="ARestrictedType">
    <xs:complexContent>
    <xs:restriction base="base:AType">
    <xs:sequence>
    <xs:element name="name" type="xs:string" />
    </xs:sequence>
    </xs:restriction>
    </xs:complexContent>
    </xs:complexType>
    </xs:schema>
    when i import this into livecyle  I'm expecting to see only restricted elements but i see all the elements from dictionary.
    Here in this case I want to see in dataview only "name", but i see both "title" and "name"
    In my actual forms "dictionary xsd" is so big which makes my livecycle designe very slow.
    As a result i get this error message, if i remove some of the elements then livecycle can import.
    Can somebody help me please.

    EMF doesn't provide any tools for doing DTD to XML Schema conversion.
    The first error sounds like there are things with names that aren't well
    formed and the second sounds like references either to a namespace that
    isn't imported or that doesn't define the referenced name.
    as13 wrote:
    > Hello,
    > I got a problem by importing an xsd schema.
    > I converted a dtd to a xsd schema first by Stylus Studio. After that i
    > tried to create a new EMF project by importing the xsd schema.
    >
    > Allways got problems like that:
    >
    > "Problems were detected while validating and converting the XML Schemas
    > Error: XSD: The value 'xxx' of attribute 'name' must conform to
    > pattern '(\i\c*) & ([\i-[:]][\c-[:]]*)' as constrained by
    > 'http://www.w3.org/2001/XMLSchema#NCName' : URI
    > file:/C:/.../EnterpriseDTD.xsd Line 21 Column 4
    >
    > or
    >
    > Error: XSD: Element reference 'UML#xxx' is unresolved : URI
    > file:/C:/.../EnterpriseDTD.xsd Line 569 Column 5
    >
    >
    > Because of the xsd Schema is about 700kB, these problems appears round
    > about 3000 times!!!
    >
    > Does anyone has an idea? I think it´s about a not valid xsd schema,
    > but I don´t know, how i can generate a valid xsd schema out of a DTD.
    > I tried it with stylus Studio an XMLSpy. Couldn´t get a "valid" Schema...
    >
    >
    >
    > greets
    >

  • Accessing WSDL gives problem..........

    Hi all,
    I'm using NWDS SP12. I'm trying to create deployable proxy out of one WSDL file, which is residing in the server that needs authentication to access that. So, when I give URL to that particular WSDL when generating proxy, I'm not able to do so. How do I give authentication parameter there???
    Then I had tried downloading that WSDL file to my local file system and tried with that also...but no luck...
    Do anyone have any idea????
    Regards,
    Mausam

    Hi Bhavik,
    Thanks for replying.
    I think that was the problem with SP11.....but in SP12 its working fine. I'm able to consume any other services, means I'm able to create proxy for other services like Google.....
    But problem here is, my WSDL file is on the server which requires authentication to access WSDL. So, when I try to give the URL of WSDL its giving HTTP 401 error(unauthorised access). So, the question is "how do I give those parameters while generating proxy for WSDL?"
    Regards,
    Mausam

  • Jaxb and xsd problem

    Hi,
    I am trying to compile a set of generated jaxb classes from the xsd defined below. During compilation I get an error stating "Nested type GuestCountType hides an enclosing type". Does anyone see a problem with my xsd file. Appreciate any help with this problem
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
         <xs:complexType name="GuestCountType">
              <xs:sequence>
                   <xs:element name="GuestCount" maxOccurs="99">
                        <xs:complexType>
                             <xs:attributeGroup ref="GuestCountGroup"/>
                        </xs:complexType>
                   </xs:element>
              </xs:sequence>
              <xs:attribute name="IsPerRoom" type="xs:boolean" use="optional"/>
         </xs:complexType>
         <xs:complexType name="RoomStayCandidateType">
              <xs:sequence>
                   <xs:element name="GuestCounts" type="GuestCountType" minOccurs="0"/>
              </xs:sequence>
         </xs:complexType>
         <xs:attributeGroup name="GuestCountGroup"/>
    </xs:schema>

    Refer to section
    E.2 Not Required XML Schema
    concepts
    "A JAXB implementation is not required to support the following XML Schema
    concepts for this version of the specification. A JAXB implementation may
    choose to support these features in an implementation dependent manner."
    E.2.2 Not supported while manipulating the XML
    content
    Schema component: wildcard
    (any)
    how can i know if an xml element with xsi:nil="true" (unmarshal)
    and set xsi:nil="true" for an element (marshal) ?
    According to the JAXB 1.0 specification:
    If {nillable} is "true", the methods setNil() and isNil() are
    generated.

  • XSD Problem during Import

    Hi! I have created a XML to load the catalog item in batch mode and I understand that I have to use a XSD. So, I got a generated copy of the XSD (using XMLSpy), added the XML schema in the MDM Console and assigned it to the appropriate Port. I then loaded the product file in the Ready folder and the file disappeared - indicating that it has been processed. An exception occurred on checking the status of the load. In the report, there is a message - Source file does not conform to XML Schema.
    I then tried to import the XML through Import Manager and am able to import without problem. However, if I do the import using XSD, I found that the data did not appear at all for the structure. I reckon that may be the reason why the batch import did not work. However, I am not sure what is wrong with the XSD. Anybody has any idea? Thanks in advance for any help rendered.
    Below are my XML data and XSD:
    <?xml version="1.0" encoding="utf-8"?>
    <ProductCatalog xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="C:\TEMP\Product Load XML.xsd">
         <MaterialContent>
              <Category>OTHER</Category>
              <MfgPartNum/>
              <MfgName/>
              <SupPartNum>9999TEST</SupPartNum>
              <SupName>Company ABC</SupName>
              <SupID>5650</SupID>
              <Description>9999 TEST ITEM</Description>
              <ScaleValue>1</ScaleValue>
              <Price>2.0</Price>
              <InfoRecord/>
              <PurOrg/>
              <Currency>NZD</Currency>
              <UOM>EA</UOM>
              <LongDescription/>
              <Picture/>
              <UNSPSC>44122011</UNSPSC>
              <UNSPSCDesc>Folders</UNSPSCDesc>
              <LeadTime>2</LeadTime>
              <Aliases/>
              <ProdGroup>00603</ProdGroup>
              <ItemType/>
              <Type/>
              <MimeType/>
              <URLDesc/>
              <URLLink/>
         </MaterialContent>
    </ProductCatalog>
    XSD:
    <?xml version="1.0" encoding="UTF-8"?>
    <!W3C Schema generated by XMLSpy v2008 rel. 2 (http://www.altova.com)>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
         <xs:element name="URLLink">
              <xs:complexType/>
         </xs:element>
         <xs:element name="URLDesc">
              <xs:complexType/>
         </xs:element>
         <xs:element name="UOM" type="xs:string"/>
         <xs:element name="UNSPSCDesc" type="xs:string"/>
         <xs:element name="UNSPSC" type="xs:int"/>
         <xs:element name="Type">
              <xs:complexType/>
         </xs:element>
         <xs:element name="SupPartNum" type="xs:string"/>
         <xs:element name="SupName" type="xs:string"/>
         <xs:element name="SupID" type="xs:short"/>
         <xs:element name="ScaleValue" type="xs:byte"/>
         <xs:element name="PurOrg">
              <xs:complexType/>
         </xs:element>
         <xs:element name="ProductCatalog">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element ref="MaterialContent" maxOccurs="unbounded"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="ProdGroup" type="xs:short"/>
         <xs:element name="Price" type="xs:decimal"/>
         <xs:element name="Picture" type="xs:string"/>
         <xs:element name="MimeType">
              <xs:complexType/>
         </xs:element>
         <xs:element name="MfgPartNum">
              <xs:complexType/>
         </xs:element>
         <xs:element name="MfgName">
              <xs:complexType/>
         </xs:element>
         <xs:element name="MaterialContent">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element ref="Category"/>
                        <xs:element ref="MfgPartNum"/>
                        <xs:element ref="MfgName"/>
                        <xs:element ref="SupPartNum"/>
                        <xs:element ref="SupName"/>
                        <xs:element ref="SupID"/>
                        <xs:element ref="Description"/>
                        <xs:element ref="ScaleValue"/>
                        <xs:element ref="Price"/>
                        <xs:element ref="InfoRecord"/>
                        <xs:element ref="PurOrg"/>
                        <xs:element ref="Currency"/>
                        <xs:element ref="UOM"/>
                        <xs:element ref="LongDescription"/>
                        <xs:element ref="Picture"/>
                        <xs:element ref="UNSPSC"/>
                        <xs:element ref="UNSPSCDesc"/>
                        <xs:element ref="LeadTime"/>
                        <xs:element ref="Aliases"/>
                        <xs:element ref="ProdGroup"/>
                        <xs:element ref="ItemType"/>
                        <xs:element ref="Type"/>
                        <xs:element ref="MimeType"/>
                        <xs:element ref="URLDesc"/>
                        <xs:element ref="URLLink"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="LongDescription">
              <xs:complexType/>
         </xs:element>
         <xs:element name="LeadTime" type="xs:byte"/>
         <xs:element name="ItemType">
              <xs:complexType/>
         </xs:element>
         <xs:element name="InfoRecord">
              <xs:complexType/>
         </xs:element>
         <xs:element name="Description" type="xs:string"/>
         <xs:element name="Currency" type="xs:string"/>
         <xs:element name="Category" type="xs:string"/>
         <xs:element name="Aliases">
              <xs:complexType/>
         </xs:element>
    </xs:schema>

    Hi I have finally resolved the problem! I did that by modifying the XSD into a simpler format which at least I can understand
    In general, I grouped the element definitions together and then put the top element at the bottom to reference to these elements. I also changed the type of some of the elements from complex to simple. Note that I didn't have to remove the namespace here.
    For those who are interested, below is the XSD I have modified from the generated XSD shown in my original posting on this problem:
    <?xml version="1.0" encoding="UTF-8"?>
    <!W3C Schema generated by XMLSpy v2008 rel. 2 (http://www.altova.com)>
    <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
    <!-- definition of elements -->
         <xs:element name="URLLink" type="xs:string"/>
         <xs:element name="URLDesc" type="xs:string"/>
         <xs:element name="UOM" type="xs:string"/>
         <xs:element name="UNSPSCDesc" type="xs:string"/>
         <xs:element name="UNSPSC" type="xs:int"/>
         <xs:element name="Type" type="xs:string"/>
         <xs:element name="SupPartNum" type="xs:string"/>
         <xs:element name="SupName" type="xs:string"/>
         <xs:element name="SupID" type="xs:short"/>
         <xs:element name="ScaleValue" type="xs:byte"/>
         <xs:element name="PurOrg" type="xs:string"/>
         <xs:element name="ProdGroup" type="xs:short"/>
         <xs:element name="Price" type="xs:decimal"/>
         <xs:element name="Picture" type="xs:string"/>
         <xs:element name="MimeType" type="xs:string"/>
         <xs:element name="MfgPartNum" type="xs:string"/>
         <xs:element name="MfgName" type="xs:string"/>
         <xs:element name="LongDescription" type="xs:string"/>
         <xs:element name="LeadTime" type="xs:byte"/>
         <xs:element name="ItemType" type="xs:string"/>
         <xs:element name="InfoRecord" type="xs:string"/>
         <xs:element name="Description" type="xs:string"/>
         <xs:element name="Currency" type="xs:string"/>
         <xs:element name="Category" type="xs:string"/>
         <xs:element name="Aliases" type="xs:string"/>
    <!-- definition of complex elements -->
         <xs:element name="MaterialContent">
              <xs:complexType>
                   <xs:sequence>
                        <xs:element ref="Category"/>
                        <xs:element ref="MfgPartNum"/>
                        <xs:element ref="MfgName"/>
                        <xs:element ref="SupPartNum"/>
                        <xs:element ref="SupName"/>
                        <xs:element ref="SupID"/>
                        <xs:element ref="Description"/>
                        <xs:element ref="ScaleValue"/>
                        <xs:element ref="Price"/>
                        <xs:element ref="InfoRecord"/>
                        <xs:element ref="PurOrg"/>
                        <xs:element ref="Currency"/>
                        <xs:element ref="UOM"/>
                        <xs:element ref="LongDescription"/>
                        <xs:element ref="Picture"/>
                        <xs:element ref="UNSPSC"/>
                        <xs:element ref="UNSPSCDesc"/>
                        <xs:element ref="LeadTime"/>
                        <xs:element ref="Aliases"/>
                        <xs:element ref="ProdGroup"/>
                        <xs:element ref="ItemType"/>
                        <xs:element ref="Type"/>
                        <xs:element ref="MimeType"/>
                        <xs:element ref="URLDesc"/>
                        <xs:element ref="URLLink"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:element name="ProductCatalog">
               <xs:complexType>
                   <xs:sequence>
                        <xs:element ref="MaterialContent" maxOccurs="unbounded"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
    </xs:schema>
    Edited by: SF on Dec 3, 2008 11:17 AM

  • WSDL, XSD files can b created?

    Hi everyone,
            hey plz answer this quest. can v create WSDL, and XSD files or v have to just use the one which are already existing.If v can create them can anyone tell me the procedure how to create it.
    thanx
      xilearner

    Hi,
    This will help you to understand how to create
    XSD :
    http://www.w3schools.com/schema/default.asp
    WSDL :
    http://www.w3schools.com/wsdl/default.asp
    Regards
    Agasthuri Doss

  • Wsdl endpoint problem

    Hi everyone, i need some help, I have a wsdl that points to an external server, if I test the wsdl in WSNavigator I need to chance the end point to "Defined by the user" and set the ip of the external server because by default is "localhost" there, my problem is that when my app execute the model, it tries to reach localhost not the ip given when the wsdl was imported. My question is how i need to import the wsdl to my app to be available to change the endpoint.
    Thanks !

    Hi
    This is how you change the endpoint dynamically in code.
    wdContext.<modelNode>().bind(<modelobject>);
                <model object>.wdSetInvocationModifier(new IWDWSInvocationModifier() {
                       public void doModifyInvocation(final Object port) {
                           if ( port instanceof Stub ) {
                             final Stub stub = (Stub)port;
                             stub._setProperty(Stub.ENDPOINT_ADDRESS_PROPERTY,<endpoint>);
                           } else if (port instanceof DInterfaceInvoker) {
                             final DInterfaceInvoker invoker = (DInterfaceInvoker)port;
                             invoker.setProperty(Stub.ENDPOINT_ADDRESS_PROPERTY, <endpoint>);
                           } else{
                              throw new RuntimeException(<Error Message>);
                         public void doModifyAfterInvocation() {}
                <modelobject>.execute();
    Hope this solves your problem.
    cheers
    Deepu

  • ColdFusion WSDL Integration Problem

    I am trying to use a thrid-party WSDL system from a CFMX 7.01
    installation on Windows 2003. A request to a simple (i.e. no
    parameters) method returns good data:
    CFML:
    <cfinvoke webservice="
    http://prod3.ogangi.com/contentManagerWS/services/Version?wsdl"
    method="getVersion" returnvariable="results">
    <cfoutput>#results#</cfoutput>
    However, using a more complex method throws an error
    everytime:
    CFML:
    <cfinvoke webservice="
    http://prod3.ogangi.com/contentManagerWS/services/Categories?wsdl"
    method="getCategory" returnvariable="results">
    <cfinvokeargument name="categoryid" value="294"/>
    <cfinvokeargument name="seller" value="jamaica"/>
    </cfinvoke>
    <cfoutput>#results#</cfoutput>
    ERROR MSG (click the link):
    http://kryptos.thefactoryi.com/bmobilepulse/error_result.cfm
    I checked the WSDL against the following validator and
    everything seems to be functioning correctly:
    http://www.mgateway.com/wsdlClient.htm
    NOTE: Using the getCategory method use "294" for categoryid
    and "jamaica" for seller.
    Using DreamWeaver, the WSDL service cannot be added to the
    Components toolbar (when using CF), but can be added when using any
    other document type (JSP, ASP VB, ASP #).
    What am I missing? I'm not an expert w/ WSDL, but after hours
    of trying other examples and tutorials I cannot figure out this
    problem. Any insight or help will be deeply appreciated!
    -jh

    there is a problem with the webservice in the
    CategoriesService.class. that is why it wont add in dreamweaver. it
    tries to validate the wsdl for coldfusion. i have also had mixed
    results with using a wsdl file that has multiple methods with the
    same name, i.e. the three getCategoryList methods in this wsdl
    file. so if you do get it working, you may want to manually edit
    the wsdl to use only one method and access the modified wsdl file
    locally on the cf server.
    hth

Maybe you are looking for