SAP Soamanager WSDL generates n0:string instead of xsd:string in 7.3

I´m using the Soamanager to create a Service for a Enterprise Service
Provider. The web service is generated based on a custom function
module. My intention is to consume a soap webservice via .net
application. Actually this works fine with the legacy BW 7.0 system.
But after we migrate the web service to the new BW 7.3 system, the web service interface is changed.
I have taken a look at the generated WSDL-file from Soamanager, the soamanager
generates the different type for string parameters. The
Import/Export parameter should be of type xsd:string, but it is
actually n0:string. but i need xsd:string for soap.
I´ve tried several datatypes in function module, e.g string,
char,....but always the same...n0:string instead of xsd:string.
Can you help on how to change the sting type in wsdl?
Thanks,

How about a slight change to the xsd? Try with the following, it seems to work fine:
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema">
   <xsd:element name="Orders" type="Orders"/>
   <xsd:complexType name="Orders">
      <xsd:choice minOccurs="0" maxOccurs="unbounded">
         <xsd:element name="ligne">
            <xsd:complexType>
               <xsd:sequence>
                  <xsd:element name="Field1" type="xsd:string" />
                  <xsd:element name="Field2" type="xsd:string" />
                  <xsd:element name="Field3" type="xsd:string" />
                  <xsd:element name="Field4" type="xsd:string" />
                  <xsd:element name="Qte" type="xsd:string" />
               </xsd:sequence>
            </xsd:complexType>
         </xsd:element>
      </xsd:choice>
   </xsd:complexType>
</xsd:schema>
You might also find this tool useful for testing such scenarios:
http://xsdvalidation.utilities-online.info/
By the way - how did you get the xsd that you are currently using?

Similar Messages

  • WSDL generated through SOAMANAGER cannot be loaded into flex

    Guys,
    I'm having a problem here where I use soamanager to generate the WSDL for a webservice named: ztestpg_ws.
    for some reason, Adobe Flex cannot load it.  Any ideas at all????
    Here is the WSDL:
      <?xml version="1.0" encoding="utf-8" ?>
    - <wsdl:definitions targetNamespace="urn:sap-com:document:sap:soap:functions:mc-style" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="urn:sap-com:document:sap:soap:functions:mc-style" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
    - <wsdl:documentation>
      <sidl:sidl xmlns:sidl="http://www.sap.com/2007/03/sidl" />
      </wsdl:documentation>
      <wsp:UsingPolicy wsdl:required="true" />
    - <wsp:Policy wsu:Id="BN_ztestpg_ws">
    - <wsp:ExactlyOne xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:sapsp="http://www.sap.com/webas/630/soap/features/security/policy" xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility">
    - <wsp:All>
    - <sp:TransportBinding>
    - <wsp:Policy>
    - <sp:TransportToken>
    - <wsp:Policy>
      <sp:HttpsToken />
      </wsp:Policy>
      </sp:TransportToken>
    - <sp:AlgorithmSuite>
    - <wsp:Policy>
      <sp:TripleDesRsa15 />
      </wsp:Policy>
      </sp:AlgorithmSuite>
    - <sp:Layout>
    - <wsp:Policy>
      <sp:Strict />
      </wsp:Policy>
      </sp:Layout>
      </wsp:Policy>
      </sp:TransportBinding>
      </wsp:All>
      </wsp:ExactlyOne>
      <saptrnbnd:OptimizedXMLTransfer uri="http://xml.sap.com/2006/11/esi/esp/binxml" xmlns:saptrnbnd="http://www.sap.com/webas/710/soap/features/transportbinding/" wsp:Optional="true" />
      </wsp:Policy>
    - <wsp:Policy wsu:Id="IF_ztestpg_ws">
    - <sapsession:Session xmlns:sapsession="http://www.sap.com/webas/630/soap/features/session/">
      <sapsession:enableSession>false</sapsession:enableSession>
      </sapsession:Session>
      <wsp:ExactlyOne xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:sapsp="http://www.sap.com/webas/630/soap/features/security/policy" xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702" xmlns:wsa="http://www.w3.org/2005/08/addressing" xmlns:wsu="http://schemas.xmlsoap.org/ws/2002/07/utility" />
      </wsp:Policy>
    - <wsp:Policy wsu:Id="OP_Ztestpg">
      <sapcomhnd:enableCommit xmlns:sapcomhnd="http://www.sap.com/NW05/soap/features/commit/">false</sapcomhnd:enableCommit>
      <sapblock:enableBlocking xmlns:sapblock="http://www.sap.com/NW05/soap/features/blocking/">true</sapblock:enableBlocking>
      <saptrhnw05:required xmlns:saptrhnw05="http://www.sap.com/NW05/soap/features/transaction/">no</saptrhnw05:required>
      <saprmnw05:enableWSRM xmlns:saprmnw05="http://www.sap.com/NW05/soap/features/wsrm/">false</saprmnw05:enableWSRM>
      </wsp:Policy>
    - <wsdl:types>
    - <xsd:schema attributeFormDefault="qualified" targetNamespace="urn:sap-com:document:sap:soap:functions:mc-style">
    - <xsd:element name="Ztestpg">
    - <xsd:complexType>
      <xsd:sequence />
      </xsd:complexType>
      </xsd:element>
    - <xsd:element name="ZtestpgResponse">
    - <xsd:complexType>
    - <xsd:sequence>
      <xsd:element name="Rc" type="xsd:int" />
      </xsd:sequence>
      </xsd:complexType>
      </xsd:element>
      </xsd:schema>
      </wsdl:types>
    - <wsdl:message name="Ztestpg">
      <wsdl:part name="parameters" element="tns:Ztestpg" />
      </wsdl:message>
    - <wsdl:message name="ZtestpgResponse">
      <wsdl:part name="parameter" element="tns:ZtestpgResponse" />
      </wsdl:message>
    - <wsdl:portType name="ztestpg_ws">
    - <wsp:Policy>
      <wsp:PolicyReference URI="#IF_ztestpg_ws" />
      </wsp:Policy>
    - <wsdl:operation name="Ztestpg">
    - <wsp:Policy>
      <wsp:PolicyReference URI="#OP_Ztestpg" />
      </wsp:Policy>
      <wsdl:input message="tns:Ztestpg" />
      <wsdl:output message="tns:ZtestpgResponse" />
      </wsdl:operation>
      </wsdl:portType>
    - <wsdl:binding name="ztestpg_ws" type="tns:ztestpg_ws">
    - <wsp:Policy>
      <wsp:PolicyReference URI="#BN_ztestpg_ws" />
      </wsp:Policy>
      <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
    - <wsdl:operation name="Ztestpg">
      <soap:operation soapAction="" style="document" />
    - <wsdl:input>
      <soap:body use="literal" />
      </wsdl:input>
    - <wsdl:output>
      <soap:body use="literal" />
      </wsdl:output>
      </wsdl:operation>
      </wsdl:binding>
    - <wsdl:service name="service">
    - <wsdl:port name="ztestpg_ws" binding="tns:ztestpg_ws">
      <soap:address location="http://jq03a010.esc.win.colpal.com:8035/sap/bc/srt/rfc/sap/ztestpg_ws/321/ztestpg_ws/ztestpg_ws" />
      </wsdl:port>
      </wsdl:service>
      </wsdl:definitions>

    the same problem generating Axis2 clients. There is no module extension for:
    cannot find a PolicyExtension to process http://www.sap.com/NW05/soap/features/commit/type assertions
    cannot find a PolicyExtension to process http://www.sap.com/NW05/soap/features/transaction/type assertions
    cannot find a PolicyExtension to process http://www.sap.com/NW05/soap/features/wsrm/type assertions
    cannot find a PolicyExtension to process http://www.sap.com/NW05/soap/features/blocking/type assertions
    hmm...
    Best regards
    T. Kis

  • 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

  • WSDL generates incorrect BAPIRET2 code in VS2005

    I have tried to import WSDL for two Web Services based on function modules into a Visual Studio C# project.
    In both cases, the WSDL generates the web service; however when I build the project, both services have syntax errors in the Reference.cs file for all components of the Bapiret2 class.
    Each component generates the following two error messages:
    "An object reference is required for the nonstatic field, method or property '<namespace>.System.get"
    and
    "'string' does not contain a definition for 'Xml'"
    In each case, the error messages refer to the line that reads:
    "[System.Xml.Serialization.XmlElementAttribute (Form=System.Xml.Schema.XmlSchemaForm.Unqualified)]"
    that precedes the "Set" & "Get" methods for each Bapiret2 class component. The errors highlight the "System" and "X,l" components following "Form=" .
    Has anyone seen this before?
    I'm using SAP 2004s with Support Stack 15, and Visual Studio 2005 SP1 with the Enterprise Services Explorer add-on.
    Thanks,
    D.

    I am working with VB project and encounter this problem.
    Now, I found the solution.
    It's may be help you. Good lucks.
    calling a sap webas 6.20 web service from .net

  • Problems with consuming SAP BW WSDL in Crystal Reports 2008

    Hello,
    I am trying to use the WSDL generated from the SAP BW in Crystal Reports 2008 using the XML and Web Services driver, but when I input the WSDL url Crystal does not interpret the url passed in as a WSDL url and the Services, Port and Method drop downs are blank.
    If I manually input the values I get the error below from Crystal
    "Logon failed.
    Details: Web Service Location is invalid
    WSDL Exception (at /wsdl:definitions/wsdl:portType/wsp:Policy): faultCode=INVALID_WSDL:Encountered unexpected element
    'Policy'."
    I know this is a valid WSDL as I have tested it with Xcelsius 2008 and I am able to get data back in Xcelsius. I found SAP note 1485601 that talks about Crystal Reports not being able to reading a WSDL generated by a SAP system.
               https://websmp230.sap-ag.de/sap/support/notes/1485601
    Based on the error message from Crystal above I feel that Crystal is unable to read the WSDL URL, has anyone else encountered this issue, if so is there a possible work around.
    We are running Crystal Reports 2008 V1 SP3 FP 3 and the SAP Integration Kit is also on the same service pack and patch level.
    Any help or insight into the issue will be very helpful.
    Thanks,
    Kumar

    Ingo,
    I am using the "XML and Web Services" connection option in Crystal Reports, and using a HTTP WSDL.Here is a sample of how WSDL url generated by SAP BW.
    http://servername:8000/sap/bc/srt/wsdl/bndg_DF6E553E117931F19C6B001560A1B616/wsdl11/allinone/ws_policy/document?sap-client=100
    We have a two structure BW query (one for keyfigures and one as characteristic structure ), I know that this will cause the structure for the characteristics to show up as a single field and each element of the structure will result in a row of data, but we need the individual elements on the structure and we were hoping to get around the MDX driver limitation by using the web service connection.
    The data in the Crystal Reports 2008 needs to be in a crosstab layout as shown below, but if we use the Crosstab expert the key figures are stacked one under the other and also we cannot get the labels from the KPI structure to show up on the Crystal Reports.
                   Characteristic Structure
                 Column1            Column2                     Column3     
    Label 1          KeyFigure 1          KeyFigure 2                    KeyFigure 3
    Label 2          KeyFigure 1          KeyFigure 2                KeyFigure 3
    Label 3          KeyFigure 1          KeyFigure 2                    KeyFigure 3
    This layout is already built in a Web Template and therefore we were planning on using the WSDL to get the layout directly into Crystal report, but I keep running into the WSDL error when I try to consume the WSDL in Crystal.
    Thanks,
    Kumar

  • Full qualified host name not appearing in url within WSDL generated from PI

    Hi
       We are on PI711  ( AIX OS ) and are stuck with an issue of the fully qualifed hostname not appearing within WSDL file  generated in PI71 for a webservice it exposes using the Integration builder
    We changed the host name in exchange profile ( all locations ) from hostname to hostname.companyname.intra and also in the ABAP stack as recommended in all OSS notes.
    We use the Integration Directory --> Sender Agreement --> Display WSDL option to generate the WSDL.
    Its to be noted that all locations ( including url for WSDL ) have the fully qualified hostname except the url within the WSDL.
    Dioes anyone come across this issue/ know which parameters to be updated on the PI server to make the url within the WSDL for the PI webservice to have the fully qualified host name ?

    HI Karthik,
    As Mentioned by Baskar donu2019t use proposed URL .. while creating WSDL in Id.. but instead provide URL in following format and use it in that place and create WSDL.. details about URL format..
    the URL format is fix. and it is simple.
    http://host:HTTPPort/XISOAPAdapter/MessagingServlet?channel=party:sendersystem:CC_sender
    in above URL provide your sender service component name instead of sender system.
    and provide SOAP sender communication channel name in place of CC_sender
    provide your PI system host and http name in place of host and https and use this..
    for more details about URL..
    Propose URL when Configuring Sender SOAP Adpater
    soap url
    Thanks,
    Bhupesh

  • WS-I compliance of wsdl generated by BPEL

    Hi All,
    I generated a very simple synchronous BPEL process with defaults, and assigned the input to the ouput. The wsdl generated is not WS-I compliant. It gives an error:-
    Assertion: BP2703
    Result
    failed
    Failure Detail Message
    Schema validation failed
    Failure Detail Message
    Schema validation failed: The element 'http://schemas.xmlsoap.org/wsdl/:definitions' has invalid content. An error occurred at , (1, 1179).
    The 'http://schemas.xmlsoap.org/ws/2003/05/partner-link/:partnerLinkType' element is not declared. An error occurred at , (1, 1179).
    The 'http://schemas.xmlsoap.org/ws/2003/05/partner-link/:role' element is not declared. An error occurred at , (1, 1211).
    The 'http://schemas.xmlsoap.org/ws/2003/05/partner-link/:portType' element is not declared. An error occurred at , (1, 1240).
    It seems to be giving an error for the partner link element!!!! I am testing this because in my project I am getting the same error. How can I make the wsdl WS-I compliant..

    Expose the WSDL from Sender Agreement or Inbound Processing in the ICO and test accordingly with SOAPUI.
    In case still you are getting the error in the sense you can prefer XMLAnonymizer bean or play with the namespaces you may have to go with the JAVA or XSLT mapping.
    XI: XML node into a string with graphical mapping?

  • WSDL generated from service that references XMLBean is invalid

    Env: Weblogic Workshop 9.2.0
    Build id: 783464
    When I validate a WSDL generated from a service that imports XMLBean classes (auto-generated by the XMLBeans Builder) it shows numerous errors including src-resolve.4.2. and ?The part ?parameters? has an invalid value ?hello? ??. All my schemas validate without error in both Workshop and XMLSpy. This happens for both the WSDL generated from the right click menu and from the auto generated WSDL located in the build sub-directory.
    Related to this problem, when I deploy the web service (for some reason I can deploy it if I don?t deploy the WSDL) sometimes I either can reach the web service and sometimes I receive a failure related to the parse of the WSDL stating java.util.NoSuchElementException as the reason.
    Has anyone else seen these kinds of problems?

    I'm going to open a support case but here are the XSDs
    There are four in total ... I have marked the top and bottom of each so you can clearly identify them.
    ---AddressData.xsd Start---
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:addr="http://www.test.org/address" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.test.org/address" elementFormDefault="qualified" attributeFormDefault="unqualified">
         <xs:complexType name="AddressType">
              <xs:sequence>
                   <xs:element name="LineOne" type="addr:LineOneType"/>
                   <xs:element name="LineTwo" type="addr:StreetAddressType" minOccurs="0"/>
                   <xs:element name="City" type="addr:CityType"/>
                   <xs:element name="State" type="addr:StateType"/>
                   <xs:element name="Zip" type="addr:ZipType"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="LineOneType">
              <xs:choice>
                   <xs:element name="StreetAddress" type="addr:StreetAddressType"/>
                   <xs:element name="POBoxAddress" type="addr:POBoxAddressType"/>
              </xs:choice>
         </xs:complexType>
         <xs:complexType name="StreetAddressType">
              <xs:sequence>
                   <xs:element name="StreetAddress" type="xs:string"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="POBoxAddressType">
              <xs:sequence>
                   <xs:element name="POBoxAddress" type="xs:string"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="CityType">
              <xs:sequence>
                   <xs:element name="City" type="xs:string"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="StateType">
              <xs:sequence>
                   <xs:element name="State" type="xs:string"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="ZipType">
              <xs:sequence>
                   <xs:element name="Zip" type="xs:string"/>
              </xs:sequence>
         </xs:complexType>
    </xs:schema>
    ---AddressData.xsd Stop---
    ---CustomerData.xsd Start---
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:cust="http://www.test.org/customerdata" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:addr="http://www.test.org/address" xmlns:pri="http://www.test.org/priority" xmlns:ndata="http://www.test.org/ndata" targetNamespace="http://www.test.org/customerdata" elementFormDefault="qualified" attributeFormDefault="unqualified">
         <xs:import namespace="http://www.test.org/priority" schemaLocation="CustomerPriority.xsd"/>
         <xs:import namespace="http://www.test.org/address" schemaLocation="AddressData.xsd"/>
         <xs:import namespace="http://www.test.org/ndata"
              schemaLocation="DataType.xsd" />
         <xs:element name="CustomerData">
              <xs:annotation>
                   <xs:documentation>
                        Comment describing your root element
                   </xs:documentation>
              </xs:annotation>
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="Customer" type="cust:CustomerType" />
                        <xs:element name="otherData1" type="ndata:newDataType" />
                        <xs:element name="secondaryAddress"
                             type="addr:AddressType" />
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:complexType name="CustomerType">
              <xs:sequence>
                   <xs:element name="name" type="cust:CustomerNameType"/>
                   <xs:element name="address" type="addr:AddressType"/>
                   <xs:element name="priority" type="pri:PriorityLevelType"/>
                   <xs:element name="data" type="cust:moreData"/>
              </xs:sequence>
         </xs:complexType>
         <xs:complexType name="CustomerNameType">
              <xs:sequence>
                   <xs:element name="lastname" type="xs:string"/>
                   <xs:element name="firstname" type="xs:string"/>
                   <xs:element name="title" type="xs:string"/>
              </xs:sequence>
         </xs:complexType>
         <xs:element name="anotherBitOfData" type="xs:gMonthDay"/>
         <xs:complexType name="moreData">
              <xs:sequence>
                   <xs:element name="data1" type="xs:string"/>
                   <xs:element name="data2" type="xs:long"/>
              </xs:sequence>
         </xs:complexType>
    </xs:schema>
    ---CustomerData.xsd Stop---
    ---CustomerPriority.xsd Start---
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:pri="http://www.test.org/priority" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.test.org/priority" elementFormDefault="qualified" attributeFormDefault="unqualified">
         <xs:element name="CustomerPriority">
              <xs:annotation>
                   <xs:documentation>Comment describing your root element</xs:documentation>
              </xs:annotation>
              <xs:complexType>
                   <xs:sequence>
                        <xs:element name="priority" type="pri:PriorityLevelType"/>
                   </xs:sequence>
              </xs:complexType>
         </xs:element>
         <xs:complexType name="PriorityLevelType">
              <xs:choice>
                   <xs:element name="Level1Value" type="xs:string"/>
                   <xs:element name="Level2Value" type="xs:string"/>
                   <xs:element name="Level3Value" type="xs:string"/>
              </xs:choice>
         </xs:complexType>
    </xs:schema>
    ---CustomerPriority.xsd Stop---
    ---DataType.xsd Start---
    <?xml version="1.0" encoding="UTF-8"?>
    <xs:schema xmlns:ndata="http://www.test.org/ndata" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:pri="http://www.test.org/priority" targetNamespace="http://www.test.org/ndata" elementFormDefault="qualified" attributeFormDefault="unqualified">
         <xs:import namespace="http://www.test.org/priority"
              schemaLocation="CustomerPriority.xsd" />
         <xs:complexType name="newDataType">
              <xs:sequence>
                   <xs:element name="pri" type="xs:string" />
              </xs:sequence>
         </xs:complexType>
    </xs:schema>
    ---DataType.xsd Stop---

  • WSDL generated by web service map

    Hi,
    I am totally new to ODSI. I noticed that the WSDL generated by the Web Service Map for a Data Service always contains two schemas in the types section, with an import directive in the first schema which refers to the second. The structure of the types section is something like this:
    <types>
    <xs:schema>
    <xs:import namespace="N1">
    </xs:schema>
    <xs:schema targetNameSpace="N1">...</xs:schema>
    </types>
    The question is : is it possible to have a single schema instead of two in a logical data service? In other words, to what extent can the WSDL be customized?
    I apologize in advance if the question is dumb, but as I have said, I am totally new to this product.
    Thank you very much for your help
    Alberto

    The request and response elements will always be generated in the form below. It cannot be customized.
    <xs:schema targetNamespace="ld:hello_ws" elementFormDefault="qualified" xmlns:stns="ld:hello_ws" ... >
    <s:element name="HelloWorld">
    <s:element name="HelloWorldResponse">
    </>
    Unless the targetnamespace for your logical data service matches, there will always need to be a second schema element.
    Your logical dataservice can have whatever schema you want.

  • WSDL generated by WSGEN contains input parameter as arg0

    Hi,
    I have deployed a webservice in weblogic 6.1, the WSDL file has been generated by the WSGEN, but the WSDL file contains the input parameter as "arg0" as shown below
    - <message name="getTempRequest">
    <part name="arg0" type="xsd:string" />
    </message>
    i need the part name should show the exact variable name in the service method.
    plz help me out in this,
    thanx,
    kamal.

    The request and response elements will always be generated in the form below. It cannot be customized.
    <xs:schema targetNamespace="ld:hello_ws" elementFormDefault="qualified" xmlns:stns="ld:hello_ws" ... >
    <s:element name="HelloWorld">
    <s:element name="HelloWorldResponse">
    </>
    Unless the targetnamespace for your logical data service matches, there will always need to be a second schema element.
    Your logical dataservice can have whatever schema you want.

  • Some strange with the WSDL generated during asadmin deploy

    Hi devs and users,
    I'have created WebService with @WebServices annotation,
    packaged and deploy it with asadmin.
    When accessing the WSDL via
    http://192.168.1.1:8080/test/TestService?WSDL
    the WSDL contain something like this:
    <types>
    <xsd:schema>
    <xsd:import namespace="http://xyz/"
    schemaLocation="http://testserver:8080/test/TestService/__container$publishing$subctx/WEB-INF/wsdl/TestService_schema1.xsd"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"/>
    </xsd:schema>
    </types>
    <service name="NotificationSystemService">
    <port name="NotificationSystemPort" binding="tns:NotificationSystemPortBinding">
    <soap:address
    location="http://testserver:8080/test/TestService"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"/>
    </port>
    </service>
    Note that, the soap:address and schemaLocation use the hostname 'testserver', but not the ip address '192.168.1.1'.
    How can I control the AS so that, when it generate the WSDL, it use the host address, instead of the hostname.

    Apple does not participate in these forums, so you will not get a reply from an Apple engineer, nor will there be any way for you to contact anyone in the iTunes or iOS engineering team.
    I do not, however, think that there is any difference between the Mac and Windows versions of iTunes in what information they transmit to Apple's services. In either version no personal information of any sort is sent when only doing an update to iOS, only to the best of my knowledge the device identification so that the correct update file can be delivered. The only time any of your contacts or any other such information would be sent to Apple's servers is if you are synchronizing via iCloud, and emails only if you use iCloud's email service.
    My understanding is that user generated data, settings and apps are handled entirely with the backup file if ones is created?
    Except for synchronizing with iCloud, that would be correct. This may be of interest:
    http://support.apple.com/kb/HT4865
    Regards.

  • Urgent Help required! - Storing the XML as String instead as a file

    Hi,
    I need urgent help on this.
    I have an XML file. I have used org.w3c.dom to build dom and manipulate the XML file.
    I have updated the values for some of the nodes and I have deleted some of the unwanted nodes.
    I am able to save the output of the DOM as another XML file using
    either transform class or XMLSerializer with OutputFormatter class.
    But my requirement is to save the output of the DOM into a String instead of a file.
    When I save it in String, I need to have the following XML decalration and DOCTYPE declration also with it.
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE Test SYSTEM "Test.dtd">
    Can anyone pls help me in this??
    Thanks in Advance. Expecting some inpputs pls....!
    Regards,
    Gayathri.

    hi,
    i think this is what u want
        public static String getXmlString(Document d) {
          StringWriter strResponse = null;
          try {
             OutputFormat format  = new OutputFormat(d);
             strResponse = new StringWriter();
             XMLSerializer serial = new XMLSerializer( strResponse, format );
             serial.asDOMSerializer();
             serial.serialize(d.getDocumentElement());
          catch (Exception e) {
            System.out.println(e.toString());
          return strResponse.toString();
    }HTH
    vasanth-ct

  • Problem: textbox leave empty string("") instead of null

    Hello, I have a problem with textboxes. By default, they always are initialized to null, but when I start entering and removing data from textboxes, many times they leave an empty string "" instead of null.
    And, of course, it's not the same a null value as an empty string and thus, I haven't got the expected result in queries to database.
    Thus, I always have to compare textbox values with "" and null. It's very tedious and not elegant solution. I would like to know if there is another way to get the values as null instead of empty strings.

    Yes. Once you entered and remove the text it will evaluated as you told .
    For ur case u can Try the condition as
    if ( instance !=null && instance.length !=0)
    be sure instance != null check b4 other wise u can get NullPointerException

  • Assign a value from an wsdl:arrayType="xsd:string[]"

    Hi to everyone, I'm new at this issue of Bpel. I'm a developing a simple process and I need to communicate my process with a Web Services that returns a wsdl:arrayType="xsd:string[]", this is the type of the wdsl of the web service:
    <complexType
    name="ArrayOfString"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    <complexContent>
    <restriction
    base="SOAP-ENC:Array">
    <attribute
    ref="SOAP-ENC:arrayType"
    wsdl:arrayType="xsd:string[]" />
    </restriction>
    </complexContent>
    </complexType>
    I need to know how to reference the values inside this response (array of string) and copy to a string variable inside my process.
    Thanks at all to everyone.
    Mulder

    Im not sure about this one, but can remember something about bpel not able to handle soap-encoded arrays.

  • Can "Save for Web" generate a thumbnail instead of an icon?

    Can "Save for Web" generate a thumbnail instead of an icon? Or can the icon be replaced by a thumbnail? Thanks.

    I don't think Save for Web embeds any icons or thumbnails, because the whole point of Save for Web is to keep the file size down as much as possible for Web use by not including anything except the image and some text metadata that you choose. If you're seeing a thumbnail or icon, it was probably generated by your operating system and may only be local to your desktop.
    If you do want to embed a thumbnail or icon into a JPEG file, you might get one by choosing File > Save As instead. The Save As command is intended to give you the most complete file possible, where Save for Web is designed to give you the smallest file possible.

Maybe you are looking for

  • Sign in front of numeric/currency field in ALV grid/list

    Dear all, We need to display sign in front for numeric/currency values which will use the sub-total functionality. Currently there is no option for doing this in ALV output options. Is this possible? regards Nitesh

  • How can I get error message when calling pl/sql

    Hi, I call a pl/sql java wrapper generated by Rosetta. public static void startWf( OracleConnection _connection, BigDecimal p_goal_header_id, BigDecimal p_submiter_userid, String p_commit, String p_init_msg_list, String [] x_return_status, BigDecimal

  • How to enter bios pavilion dv7

    I cannot figure out how to enter bios on my pavilion dv7-1135NR, i need to figure out how to change boot order!

  • EDT and BDT data transfer tool...

    Hi, I am working in insurance module of SAP. There is a business object called Business Partner which we need to migrate from legacy to R/3. Now for migration of Business partner generally LSMW is not used. People here use EDT (External data transfer

  • Asynchronous  IO ( need help)

    hi i got a problem in reading a file Asynchronously, my requirements are : i would like to read huge file into the buffers (say 3 here )each buffer of fixed size ,the moment the buffer gets filled with read content ,i need to update the bufferd conte