Loading XSD Schemas as External Definition
Hi all,
I am trying to load an XSD Schema into XI. As part of this schema is another external reference. I have also loaded this into XI. Looking at the 'External References' tab of the first message, I can see the reference to the second message. The problem is when I use this definition in my Message Mapping. There is not structure being seen. Has anyone else seen this before.
The XSD schemas can be loaded into XMLSpy fine.
Thanks
Martin
Hi,
If you have tried generating this XSD using XMLspy,
check the radio button "use complex elements" attribute instead of "individual elements". This will solve your problem.
Regards,
Siva Maranani
Similar Messages
-
"Messages" problem after importing .xsd file as external definition
Hello,
I received an .xsd file from a customer and need to import it as an "External Definition" in order to create the "Message Interface". The structure of the xsd looks like this:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:px="http://www.opentrans.org/XMLSchema/1.0" targetNamespace="http://www.opentrans.org/XMLSchema/1.0" elementFormDefault="qualified">
<xsd:element name="ORDER">
</xsd:element>
<xsd:element name="ADDRESS">
</xsd:element>
<xsd:element name="ARTICLE_ID">
</xsd:element>
</xsd:schema>
After importing and looking at the tab "Messages" I get numerous entries, for each <xsd:element> I get one message! But I basically only need one "Message" that holds my complete xsd-file.
I tried inserting <xsd:element name="COMPLETEORDER"> right after the <xsd:schema>-Tag but that didn't work either. Somehow I need to sum up all the <xsd:elements>.
Does anyone have an idea? Thank you very much!
PeterHello Prateek, Hello everyone,
I now know what the problem is. I downloaded XMLspy and checked on the structure:
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:px="http://www.opentrans.org/XMLSchema/1.0" targetNamespace="http://www.opentrans.org/XMLSchema/1.0" elementFormDefault="qualified">
<xsd:element name="ORDER">
</xsd:element>
<xsd:element name="ADDRESS">
</xsd:element>
<xsd:element name="ARTICLE_ID">
</xsd:element>
<xsd:simpleType name="dtBOOLEAN">
</xsd:simpleType>
<xsd:simpleType name="dtCOUNTRIES">
</xsd:simpleType>
<xsd:element name="SUPPLIER_AID">
</xsd:element>
<xsd:simpleType name="typeSUPPLIER_AID">
</xsd:simpleType>
</xsd:schema>
Between the long list of <xsd:element> tags there are some simpleTypes on the same
level. Now if I insert
<xsd:element name="COMPLETEORDER">
<xsd:complexType>
<xsd:sequence>
on top, the <xsd:sequence> would be on the same level as the simpleTypes - which is not valid!
But can I just move all the simpleTypes, e.g. into an <xsd:element>??
That would be changing the customer's structure which I think is not a good thing!?
Thank you again for your help! I really appreciate it!
Best regards,
Peter -
I am trying to import the following XSD as an External Definition in Repository.
I am getting the following Error. Please help me.
Error
Activation of the change list canceled
Check result for External Definition Request | http://ABC.COM: Document check found errors
Cause: The loaded document does not contain valid XML
Error when parsing XML document com.sap.aii.utilxi.xml.xdom.XDOMException$ParseError: Error when parsing the XML document (External entity from address http://xml.cxml.org/schemas/cXML/1.2.014/cXML.dtd in XML document is not supported
XSD
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE cXML SYSTEM "http://xml.cxml.org/schemas/cXML/1.2.014/cXML.dtd">
<cXML payloadID="[email protected]"
timestamp="2005-01-13T00:00:16+00:00">
<Header>
<From>
<Credential domain="NetworkId">
<Identity>AN13000000259</Identity>
</Credential>
</From>
<To>
<Credential domain="NetworkId">
<Identity>AN01000000001</Identity>
</Credential>
</To>
<Sender>
<Credential domain="NetworkId">
<Identity>AN13000000259</Identity>
<SharedSecret>abracadabra</SharedSecret>
</Credential>
<UserAgent>Our Procurement System 3.0</UserAgent>
</Sender>
</Header>
<Request>
<GetPendingRequest lastReceivedTimestamp="2005-01-12T00:00:25+00:00"
maxMessages="20">
<MessageType>StatusUpdateRequest</MessageType>
</GetPendingRequest>
</Request>
</cXML>Hi,
The structure that you posted dose'nt look like XSD its like a XML. Actually you have created a Schema based on DTD and not XSD. Did you use Altova to create this, then please select W3Schema instead of DTD while creating it.
The following is the strucutre I got when I created using the XML you have posted.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified">
<xs:complexType name="CredentialType">
<xs:sequence>
<xs:element ref="Identity"/>
<xs:element name="SharedSecret" type="xs:string" minOccurs="0"/>
</xs:sequence>
<xs:attribute name="domain" type="xs:string" use="required"/>
</xs:complexType>
<xs:element name="Identity" type="xs:string"/>
<xs:element name="cXML">
<xs:complexType>
<xs:sequence>
<xs:element name="Header">
<xs:complexType>
<xs:sequence>
<xs:element name="From">
<xs:complexType>
<xs:sequence>
<xs:element name="Credential" type="CredentialType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="To">
<xs:complexType>
<xs:sequence>
<xs:element name="Credential" type="CredentialType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Sender">
<xs:complexType>
<xs:sequence>
<xs:element name="Credential" type="CredentialType"/>
<xs:element name="UserAgent" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="Request">
<xs:complexType>
<xs:sequence>
<xs:element name="GetPendingRequest">
<xs:complexType>
<xs:sequence>
<xs:element name="MessageType" type="xs:string"/>
</xs:sequence>
<xs:attribute name="lastReceivedTimestamp" type="xs:string" use="required"/>
<xs:attribute name="maxMessages" type="xs:string" use="required"/>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
<xs:attribute name="payloadID" type="xs:string" use="required"/>
<xs:attribute name="timestamp" type="xs:string" use="required"/>
</xs:complexType>
</xs:element>
</xs:schema>
Thanks,
Prakash -
Hi All,
I have imported xsd files as external definitions. They are showing messaages list without any space.While using them in message mapping they are not showing the fields. Even in the case of direct import into message mapping also the same result.I am not getting the problem. Any suggestions to solve this..
Thanks in advance,
Kartikeyahi,
i think this helps..
some of the tags are not supported by message mapping...like choice and complex..
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2089f29b-b10a-2a10-5297-e258df0c1bfc
Thanks,
vijaya. -
Error importing xsd as external definition
I'm importing a wsdl file as external definition and it references some xsd files that I'm trying to import too. Specifically there are 2 of them that I can't import in PI, as I get the next error:
Error when loading XML document (Failed to load resource from the context classloader of the current thread! Loading from classloader was caused by: java.net.UnknownHostException: www.w3.org)
XSD files might be found under next urls:
[XAdES.xsd|https://www3.aeat.es/ADUA/internet/es/aeat/dit/adu/xades/XAdES.xsd]
[xmldsig-core-schema.xsd|https://www3.aeat.es/ADUA/internet/es/aeat/dit/adu/xades/xmldsig-core-schema.xsd]
and are meant to be used to sign the document.
I have validated the files using the service in the next url:
[http://www.w3.org/2001/03/webdata/xsv|http://www.w3.org/2001/03/webdata/xsv] as well as in Altova XML Spy.
Has anyone any idea of what the problem might be? It is really interfering in my development.
Thanks in advance.Ok I think I might have solved it. First there was a pair of problems with the file xmldsig-core-schema.xsd.
1. The name couldn't be used in PI as '-' characters are not allowed.
I changed the name to xmldsig_core_schema.xsd
2. The file had these lines at the start:
<!DOCTYPE schema PUBLIC "-//W3C//DTD XMLSchema 200102//EN" "http://www.w3.org/2001/XMLSchema.dtd" [
<!ATTLIST schema
xmlns:ds CDATA #FIXED "http://www.w3.org/2000/09/xmldsig#"
>
<!ENTITY dsig 'http://www.w3.org/2000/09/xmldsig#'>
<!ENTITY % p ''>
<!ENTITY % s ''>
]>
PI doesn't like that if you import the file as XSD because I guess that is DTD not XSD format.
I removed those lines.
With these two changes this file could be imported.
However I still had problems with the XAdES.xsd file. PI couldn't recognize the import of xmldsig-core-schema.xsd file:
<xsd:import namespace="http://www.w3.org/2000/09/xmldsig#" schemaLocation="http://www.w3.org/TR/2002/
REC-xmldsig-core-20020212/xmldsig-core-schema.xsd"/>
It didn't like the URL, so I changed it to make reference to my local file.
After this, it all worked. The question is, will it also work in runtime when I'll make use of these external definitions created? Or will my changes have an impact on the results? I guess it will work fine but perhaps I'm wrong.
Besides, when activated I got the next warning:
Name of '/schema/complexType("TimeStampType")/sequence/choice/element("XMLTimeStamp")' starts with 'xml'
There's an element name that starts by XML. Is this forbidden? Will I have problems if I activate and use it just as it is?
Thanks for the answers. -
XSD Resolution problem - Unable to load Translation schemas
Hi,
I've run into a very strange kind of problem (not to say some are less strange then others). Let me explain the context of the situation.
I've got a BPEL process calling two plsql packages on ORA database, one Java web service running on the same weblogic server and couple of other services (eg. notification services, jdbc select/insert, etc.). There is no problem with the last listed, but definitely something wrong with the web service and the plsql callouts.
When I deploy the BPEL process and execute it, the first two instances always fail. The same happens when I restart the server, the errors are repeated after a certain period as well (for example over night). The process always fails EXACTLY TWICE, before running normally. Every other instance executed after the two initial failures runs WITHOUT the following error.
I mentioned there are two plsql callouts in the process, earlier the first instance failed on the second one and the second instance failed on the first. Now, it mostly fails on the second callout. I've made no significant changes in the code. Perhaps the strangest thing about this is that it fails when invoking the plsql package but the error concerns xsd definitions of the web service that plays no role at this stage.
All my services are correctly deployed, I deleted all interface definitions from MDS repository and redeployed SOA bundle again before installing each service.
I think it has something to do with generated xsd definitions by the java web service (it's the http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 and http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 from following stack trace), but I can't figure out what exactly is wrong with them.
Anybody come accross a similar error? Thanks for tips, I've run out of ideas.
Error Message: {http://schemas.oracle.com/bpel/extension}bindingFault
Fault ID default/S50001KontrolaSouboruBS!1.0*soa_be986963-f9d9-412d-b692-43804a35b3ee/KontrolaSouboru/830023-BpInv18-BpSeq8.12-2
Fault Time 14-Feb-2012 11:11:16
Non Recoverable System Fault :
<bpelFault><faultType>0</faultType><bindingFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="summary"><summary>Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "JCA Binding execute of Reference operation 'LogFile' failed due to: Exception occured when binding was invoked. Exception occured during invocation of JCA binding: "Could not instantiate InteractionSpec oracle.tip.adapter.db.DBStoredProcedureInteractionSpec due to: XSD Resolution problem. XSD Resolution problem. Unable to load Translation schemas from for http://xmlns.oracle.com/pcbpel/adapter/db/TST_IP/LOG_FILE/LOG_FILE/ due to: Different schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and oramds:/apps/LCRInterface/DataObjects/Common/V1/Common.xsd elementFormDefault values are differentDifferent schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and http://localhost:8001/soa-infra/services/default/S50035NotifikaceChybyBS/apps/LCRInterface/DataObjects/Common/V1/Common.xsd elementFormDefault values are differentDifferent schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and oramds:/apps/LCRInterface/DataObjects/Common/V1/DataTypes.xsd elementFormDefault values are differentDifferent schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and http://localhost:8001/soa-infra/services/default/S50035NotifikaceChybyBS/apps/LCRInterface/DataObjects/Common/V1/DataTypes.xsd elementFormDefault values are differentGlobal element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListByMaskRespDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 7] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 82] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:7] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:82] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 9] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 36] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:9] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:36] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}SaveFileDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 19] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 21] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:19] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:21] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListRespDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 11] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 51] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:11] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:51] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListByMaskDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 5] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 66] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:5] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:66] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetTextFileDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 13] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 112] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:13] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:112] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetTextFileRespDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 15] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 127] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:15] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:127] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}RenameFileDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 17] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 97] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:17] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:97] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListRespDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 115] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 52] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:117] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:54] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}RenameFileDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 175] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 98] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:177] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:100] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetTextFileRespDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 153] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 128] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:155] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:130] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListByMaskRespDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 64] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 83] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:66] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:85] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}SaveFileDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 93] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 22] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:95] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:24] Please make sure all used XML schemas are imported/included correctly. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. ". The invoked JCA adapter raised a resource exception. Please examine the above error message carefully to determine a resolution. </summary></part><part name="detail"><detail>Different schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and oramds:/apps/LCRInterface/DataObjects/Common/V1/Common.xsd elementFormDefault values are differentDifferent schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and http://localhost:8001/soa-infra/services/default/S50035NotifikaceChybyBS/apps/LCRInterface/DataObjects/Common/V1/Common.xsd elementFormDefault values are differentDifferent schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and oramds:/apps/LCRInterface/DataObjects/Common/V1/DataTypes.xsd elementFormDefault values are differentDifferent schema default values detected between: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=2 and http://localhost:8001/soa-infra/services/default/S50035NotifikaceChybyBS/apps/LCRInterface/DataObjects/Common/V1/DataTypes.xsd elementFormDefault values are differentGlobal element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListByMaskRespDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 7] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 82] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:7] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:82] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 9] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 36] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:9] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:36] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}SaveFileDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 19] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 21] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:19] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:21] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListRespDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 11] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 51] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:11] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:51] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListByMaskDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 5] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 66] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:5] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:66] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetTextFileDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 13] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 112] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:13] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:112] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetTextFileRespDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 15] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 127] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:15] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:127] Global element declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}RenameFileDM' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 17] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 97] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:17] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:97] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListRespDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 115] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 52] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:117] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:54] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}RenameFileDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 175] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 98] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:177] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:100] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetTextFileRespDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 153] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 128] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:155] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:130] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}GetFileListByMaskRespDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 64] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 83] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:66] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:85] Global Type declaration/definition of name '{http://xmlns.lesycr.cz/DO/PrenosSouboru/V1}SaveFileDataType' are duplicated at the following locations: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [line#: 93] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [line#: 22] There are at least two of them looking different: http://localhost:8001/S50040PrenosSouboruBS/PrenosSouboruBSSOAP11BindingPort?xsd=1 [difference starting at line#:95] oramds:/apps/LCRInterface/DataObjects/D500Proces/PrenosSouboru/V1/PrenosSouboruDM.xsd [difference starting at line#:24] </detail></part><part name="code"><code>null</code></part></bindingFault></bpelFault>I had similar issue, when i deployed composite using Jdeveloper. The problem was with my adf-config.xml pointing to dev server and all my references in my composite.xml referring to test server.
I changed property of 'oracle.mds.persistence.stores.db.DBMetadataStore' in adf-config.xml to test server. After adf-config.xml change in Jdev my compilation went smooth.
Note: If above changes doesn't work, try restarting JDeveloper, sometimes the changes in adf-config.xml is not getting effect immediately.
Regards,
Ziaur Rahuman S
Edited by: Ziaur Rahuman on Feb 13, 2013 10:58 PM -
Problem Loading WSDL in External Definition
Hello people,
i'm having some problems When i'm Importing the WSDL in external definitions, the Messages are not being Recognized, it doesnt load the message structures, if i try in any other program that uses the WSDL like SoapUI, the wsdl works fine.
Here is the WSDL links
http://siatepqa.suseso.cl:8888/Siatep/WSToken?wsdl
http://siatepqa.suseso.cl:8888/Siatep/WSIngreso?wsdl
http://siatep.suseso.cl:8888/SusesoSiatep/WSToken?wsdl
http://siatep.suseso.cl:8888/SusesoSiatep/WSIngreso?wsdl
anyone can help?Hi,
http://siatepqa.suseso.cl:8888/Siatep/WSToken?wsdl
I checked the WSDL from the above link. The issue that I noticed is that you are importing the schema structure in your above WSDL. PI is unable to recognize the external reference. SOAPUI (or similar tool) will recognize the external reference.
Best option is that you should re-modify your above WSDL and provide the schema in this WSDL itself. It should then work just fine.
Hope this helps.
Regards,
Neetesh -
How to see structure under schema when Create External Definition
Hi ...we have scenario like RFC<>XI<>SOAP
The request payload(SOAPIN) for SOAP is:
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<AddressValidator xmlns="http://tempuri.org/geostan3/AddressValidator">
<LicenseFile>string</LicenseFile>
<Z9Path>string</Z9Path>
<House>string</House>
<Street>string</Street>
</soap:Body>
</soap:Envelope>
and we are expecting response message from SOAP:
diffgr:diffgram xmlns:msdata="urn:schemas-microsoft-com:xml-msdata" xmlns:diffgr="urn:schemas-microsoft-com:xml-diffgram-v1">
- <AddressCheck xmlns="">
- <Address diffgr:id="Address1" msdata:rowOrder="0" diffgr:hasChanges="inserted">
<Addline1>220 W MAIN ST</Addline1>
<Addline2 />
<URB />
<Lastline>LOUISVILLE, KY 40202-1395</Lastline>
<Location>-85754010, 38256144</Location>
<OutBlock>211110049001067</OutBlock>
<OutCBSA>31140</OutCBSA>
<MatchCode>SE0</MatchCode>
<LocationCode>AS0</LocationCode>
<DPVConfirm />
<FootNote1 />
<FootNote2 />
<FootNote3 />
<Msg>OK</Msg>
</Address>
</AddressCheck>
so when we created external definition using wsdl file into XI, it showing only schema as SOAPOUT (I couldn't see those fields in XI/under schema).
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<AddressValidatorResponse xmlns="http://tempuri.org/geostan3/AddressValidator">
<AddressValidatorResult>
<xsd:schema>schema</xsd:schema>xml</AddressValidatorResult>
</AddressValidatorResponse>
</soap:Body>
</soap:Envelope>
SXMB_MONI showing(Response):
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:AddressValidatorResponse xmlns:ns0="http://tempuri.org/geostan3/AddressValidator">
- <ns0:AddressValidatorResult>
<ns1:schema xmlns:ns1="http://www.w3.org/2001/XMLSchema" />
</ns0:AddressValidatorResult>
</ns0:AddressValidatorResponse>
So my question is how do I map response fields to RFC response? Auctully this schema is like table structure which is having all response fields.
I could see all response structure with data in sxmb_moni-->Response Msg ID > inbound message>payloads(main document). Is there any way to send this response to RFC ?
or can you suggest me any other way to send this response to RFC.
Thanks,
Edited by: PILearn on Jun 2, 2008 10:21 PMHere you go..
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://tempuri.org/geostan3/AddressValidator" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" targetNamespace="http://tempuri.org/geostan3/AddressValidator" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
<wsdl:types>
<s:schema elementFormDefault="qualified" targetNamespace="http://tempuri.org/geostan3/AddressValidator">
<s:import namespace="http://www.w3.org/2001/XMLSchema" />
<s:element name="AddressValidator">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="LicenseFile" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="LicensePassword" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="SearchPath" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Z9Path" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="House" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Street" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="AddLine2" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="AddLastLine" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="URB" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Matchmode" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="Datum" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="AddressValidatorResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="AddressValidatorResult">
<s:complexType>
<s:sequence>
<s:element ref="s:schema" />
<s:any />
</s:sequence>
</s:complexType>
</s:element>
</s:sequence>
</s:complexType>
</s:element>
<s:element name="DataSet" nillable="true">
<s:complexType>
<s:sequence>
<s:element ref="s:schema" />
<s:any />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="AddressValidatorSoapIn">
<wsdl:part name="parameters" element="tns:AddressValidator" />
</wsdl:message>
<wsdl:message name="AddressValidatorSoapOut">
<wsdl:part name="parameters" element="tns:AddressValidatorResponse" />
</wsdl:message>
<wsdl:message name="AddressValidatorHttpGetIn">
<wsdl:part name="LicenseFile" type="s:string" />
<wsdl:part name="LicensePassword" type="s:string" />
<wsdl:part name="SearchPath" type="s:string" />
<wsdl:part name="Z9Path" type="s:string" />
<wsdl:part name="House" type="s:string" />
<wsdl:part name="Street" type="s:string" />
<wsdl:part name="AddLine2" type="s:string" />
<wsdl:part name="AddLastLine" type="s:string" />
<wsdl:part name="URB" type="s:string" />
<wsdl:part name="Matchmode" type="s:string" />
<wsdl:part name="Datum" type="s:string" />
</wsdl:message>
<wsdl:message name="AddressValidatorHttpGetOut">
<wsdl:part name="Body" element="tns:DataSet" />
</wsdl:message>
<wsdl:message name="AddressValidatorHttpPostIn">
<wsdl:part name="LicenseFile" type="s:string" />
<wsdl:part name="LicensePassword" type="s:string" />
<wsdl:part name="SearchPath" type="s:string" />
<wsdl:part name="Z9Path" type="s:string" />
<wsdl:part name="House" type="s:string" />
<wsdl:part name="Street" type="s:string" />
<wsdl:part name="AddLine2" type="s:string" />
<wsdl:part name="AddLastLine" type="s:string" />
<wsdl:part name="URB" type="s:string" />
<wsdl:part name="Matchmode" type="s:string" />
<wsdl:part name="Datum" type="s:string" />
</wsdl:message>
<wsdl:message name="AddressValidatorHttpPostOut">
<wsdl:part name="Body" element="tns:DataSet" />
</wsdl:message>
<wsdl:portType name="AddressCheckSoap">
<wsdl:operation name="AddressValidator">
<wsdl:input message="tns:AddressValidatorSoapIn" />
<wsdl:output message="tns:AddressValidatorSoapOut" />
</wsdl:operation>
</wsdl:portType>
<wsdl:portType name="AddressCheckHttpGet">
<wsdl:operation name="AddressValidator">
<wsdl:input message="tns:AddressValidatorHttpGetIn" />
<wsdl:output message="tns:AddressValidatorHttpGetOut" />
</wsdl:operation>
</wsdl:portType>
<wsdl:portType name="AddressCheckHttpPost">
<wsdl:operation name="AddressValidator">
<wsdl:input message="tns:AddressValidatorHttpPostIn" />
<wsdl:output message="tns:AddressValidatorHttpPostOut" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="AddressCheckSoap" type="tns:AddressCheckSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" />
<wsdl:operation name="AddressValidator">
<soap:operation soapAction="http://tempuri.org/geostan3/AddressValidator/AddressValidator" style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding name="AddressCheckHttpGet" type="tns:AddressCheckHttpGet">
<http:binding verb="GET" />
<wsdl:operation name="AddressValidator">
<http:operation location="/AddressValidator" />
<wsdl:input>
<http:urlEncoded />
</wsdl:input>
<wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:binding name="AddressCheckHttpPost" type="tns:AddressCheckHttpPost">
<http:binding verb="POST" />
<wsdl:operation name="AddressValidator">
<http:operation location="/AddressValidator" />
<wsdl:input>
<mime:content type="application/x-www-form-urlencoded" />
</wsdl:input>
<wsdl:output>
<mime:mimeXml part="Body" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="AddressCheck">
<wsdl:port name="AddressCheckSoap" binding="tns:AddressCheckSoap">
<soap:address location="http://sap-ccs-geo02/geostan3/AddressValidator.asmx" />
</wsdl:port>
<wsdl:port name="AddressCheckHttpGet" binding="tns:AddressCheckHttpGet">
<http:address location="http://sap-ccs-geo02/geostan3/AddressValidator.asmx" />
</wsdl:port>
<wsdl:port name="AddressCheckHttpPost" binding="tns:AddressCheckHttpPost">
<http:address location="http://sap-ccs-geo02/geostan3/AddressValidator.asmx" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions> -
I've loaded external definition which has encoding UTF-8 but when i loaded the XSD it shows that its ISO-8859-1. Why is it changing the encoding?
Thanks,
KalpanaI dont think so. Please let us know if you observe any issues during the testing.
But it shouldnt cause problems mostly. -
PI does not keep sequence of XSD for external definition
Hi,
currently I face following problem. I have an XSD which decribes a MSCONS market message that contains following sequence:
<xs:complexType name="MSCONS">
<xs:sequence>
<xs:element name="UNH" type="UNH"/>
<xs:element name="BGM" type="BGM"/>
<xs:element name="DTM" type="DTM"/>
<xs:element name="NAD" type="NAD" minOccurs="2" maxOccurs="2"/>
<xs:element name="UNS" type="UNS"/>
<xs:element name="NAD" type="NAD" maxOccurs="unbounded"/>
<xs:element name="CNT" type="CNT" minOccurs="0" maxOccurs="99"/>
<xs:element name="UNT" type="UNT"/>
</xs:sequence>
</xs:complexType>
There are 2 NAD elements, followed by an UNS element, followed by an NAD element again. When I upload that XSD to PI as an external definition, the message is described as:
MSCONS Message
-> MSCONS Element MSCONS 1 Metered services consumption report message
-> -> UNH Element UNH 1
-> -> BGM Element BGM 1
-> -> DTM Element DTM 1
-> -> NAD Element NAD 1..unbounded
-> -> UNS Element UNS 1
-> -> CNT Element CNT 0..99
-> -> UNT Element UNT 1
All the NAD elements are summarized before UNS element. After mapping I will get an message which is not valid to XSD, because sequence is not correct.
Does anyone knows a solution/workaround for that issue. Would appreciate you help.
Thank you and Best Regards,
Nico> All the NAD elements are summarized before UNS element. After mapping I will get an message which is not valid to XSD, because sequence is not correct.
>
> Does anyone knows a solution/workaround for that issue. Would appreciate you help.
No. There is no way. The way how graphical mapping works internally makes it impossible to achieve your requirement.
As work around use two different nodes NDA and NAD1 and rename it with a simple Java mapping as second mapping step. -
External Definition (wsdl) with abstract xsd element
Hello All,
we are trying to call a webservice, here is the wsdl:
https://www.1link.com/fr/demo-sn/site/gaiwebservice.asmx?WSDL
the problem is that the GAIJobLine element is defined as abstract:
<s:complexType name="GAIJobLine" abstract="true">
and there several elements which are extending GAIJobLine, for example:
<s:complexType name="GAITyreLine">
<s:complexContent mixed="false">
<s:extension base="tns:GAIJobLine">
So in our mapping we need to map to those element which are extending base element and not to the abstract one, but Graphical mapping displays only GAIJobLIne base element.
Does anybody know how we can map to extended elements without mannually changing wsdl?
Best Regards,
Artsiom Anichenkathanks for your reply!
the extended elements are seen when I open wsdl in XMLSpy.
they are also visible in external definition object, but the main problem is that in the mapping only the base lement is displayed and there is no possobility to choose the extension.
Maybe this kind os XSDs (with abstract base types and extended elements) are just not supported by PI711? -
Error while loading xsd as external defination in IR
Hi,
When I try to create external definition from XSD,
it gives following error
"ORA-01652: unable to extend temp segment by 128 in tablespace PSAPTEMP"
This happens when I try to save any XSD.I am sure there is no problem with XSD.
Did anyone come accross this problem?
Thanks
Sachin KAs said by Arun it is an issue with internal oracle tables.
See this note : 1186364
Here is the encapsulated details of the above sap note :
Symptom
Siebel GDQL
Siebel GDQL 2.11c
Siebel GDQL 2.00c
ORA-01652
Unable to extend temp segment by 128 in tablespace TEMP '
ORA-01652: unable to extend temp segment by 128 in tablespace TEMP '
ActivateInputFields::ExecuteQuery Failure. Msg: 'An error has occurred executing a Sql statement.
Error: ActivateInputFields::ExecuteQuery Failure. Msg: 'An error has occurred executing a Sql statement. Please continue or ask your systems administrator to check your application configuration if the problem persists.
ORA-01652: unable to extend temp segment by 128 in tablespace TEMP '
Resolution
This is an Oracle error. The TEMP tablespace will need to be increased (change the file name and size as appropriate.)
For example: The SQL command to do that will look similar to:
alter database datafile 'e:\oracle\oradata\hor7\siebel_temp.dbf' resize 2000M;
Thanks
farooq. -
Can't use Data type created with External Definition
Hi,
In the repository, I would like to transport a very complexe DataType from one XI system to an other one. As I don't want to spend a week to create data types, I created a new External Definitions and loaded my XSD schema (that I exported as XSD from Source system) with Messages parameter set to "From All Available Global Elements". I don't set the "Source". I can see the "Imported Document" and "WSDL", but the Messages and External References tabs are empty. Furthermore, I can't use my new message type in a Outbound Asyncrhronous Message Interface.
Here is a very small XSD file that I use to test my scenario.
<?xml version="1.0" encoding="ISO-8859-1"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://veilleux.1" targetNamespace="http://veilleux.1">
<xsd:complexType name="SimpleType1">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
bdfdbef1df9711daa2c9001125f86068
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Name" type="SimpleType2">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
bdfdbef0df9711daa821001125f86068
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="SimpleType2">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
0fecc852df9811da899a000f206d294f
</xsd:appinfo>
</xsd:annotation>
<xsd:sequence>
<xsd:element name="Name" type="xsd:string">
<xsd:annotation>
<xsd:appinfo source="http://sap.com/xi/TextID">
ac58afc0df9711da86af001125f86068
</xsd:appinfo>
</xsd:annotation>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
Any one can help me please.
Thanks, DavyHello Moorthy,
My XSD is correct since it's XI itself that generated it from real Data Type on my source System (but I tested it in Internet Explorer and it looks fine).
I tried to select my ExternalDefinition as source in MessageMapping, but XI doesn't let me specify it (Apply button is disabled when I select my ExternalDefinition).
I'm pretty sure that it is related to the fact that I should have a Data Type in "Messages" and "External References" tabs and I have nothing. My XSD is legal, but it seems that XI can't automatically create the data type from it.
Do you have any other idea?
Thanks, Davy -
Add new field in External Definition
Hi,
I have a scenario where I have to add just one extra field in in the Outbound DT.
In our case we do not have DT, but External Definition say BAPI_XYZ.xsd
I export the .xsd file from Tools --> Export Original Document (Category: xsd, Messages:From All available global elements" )and the BAPI_XYZ.xsd is saved in my desktop.
I just add this piece of code in the place where I need it.
<xsd:element name="PLANNING_VER" minOccurs="0"><xsd:simpleType><xsd:restriction base="xsd:string"><xsd:maxLength Value="8"/></xsd:restriction></xsd:simpleType></xsd:element>
After this I import the XSD and save it undre external definition. But when I open this new xsd in the message mapping I get the error "BAPI_XYZ has No messages" and the structure is not loaded.
In the existing External definition when I move to the "Messages" Tab I can see an entry "BAPI_XYZ.Response" . The same is not available when I add the extra field and impor the new XSD
Can some one pls help??
Regards
PrasannaHi Prasanna
There is an issue with XSD. Value = "8" should be small v.
Please insert the below code at correct position.
<xsd:element name="PLANNING_VER" minOccurs="0">
<xsd:simpleType>
<xsd:restriction base="xsd:string">
<xsd:minLength value="8" />
</xsd:restriction>
</xsd:simpleType>
</xsd:element>
After that check that XSD is well formed and valied or not. You can use Validator for XML Schema W3C [Link|http://www.w3.org/2001/03/webdata/xsv] , XML editor (XMLspy), Eclipse, NetBeans.
Regards,
Raghu_Vamsee -
Unable to see Messages in External Definitions
I imported the WSDL below and created a Message Interface based on JobSubmitRequest but, when I come to map to it, all I see in the tree structure is node 'JobSubmitRequest' with elements 'parameter' and 'request_header'.
I also cannot see any messages in External Definitions.
Can anyone help with a solution?
<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xoa="http://xoa.xpedite.com/2004/11/xoa" xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://xoa.xpedite.com/2004/11/xoa">
<types>
<xs:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://xoa.xpedite.com/2004/11/xoa" xmlns="http://xoa.xpedite.com/2004/11/xoa">
<!-- address type enum -->
<xs:simpleType name="AddressType">
<xs:restriction base="xs:string">
<xs:enumeration value="fax"/>
<xs:enumeration value="internet"/>
<xs:enumeration value="mbox"/>
<xs:enumeration value="x400"/>
<xs:enumeration value="telex"/>
<xs:enumeration value="cablegram"/>
<xs:enumeration value="mailgram"/>
<xs:enumeration value="ddd"/>
<xs:enumeration value="dedLine"/>
<xs:enumeration value="softswitch"/>
<xs:enumeration value="voice"/>
<xs:enumeration value="sms"/>
<xs:enumeration value="fod"/>
<xs:enumeration value="list"/>
<xs:enumeration value="smQuery"/>
</xs:restriction>
</xs:simpleType>
<!--includes for standalone validation
<xs:include schemaLocation="StatusType.xsd"/>
================ -->
<xs:element name="AuthenticateRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="Domain" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- The authenticate result (used to send back results for synchronous and asynchronous requests) -->
<xs:element name="AuthenticateResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- includes for standalone validation
<xs:include schemaLocation="StatusType.xsd"/>
================ -->
<xs:element name="CFSCreateDirRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="RelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CFSCreateDirResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- includes for standalone validation
<xs:include schemaLocation="StatusType.xsd"/>
================ -->
<xs:element name="CFSDeleteRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="RelativePath" type="xs:string"/>
<xs:element minOccurs="0" name="DeleteDir" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CFSDeleteResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- includes for standalone validation
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
<xs:include schemaLocation="StatusType.xsd"/>
<xs:include schemaLocation="Document.xsd"/>
================ -->
<xs:element name="CFSDownloadRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="RelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CFSDownloadResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
<xs:element minOccurs="0" name="FileData" type="xoa:DocDataType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- includes for standalone validation
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
<xs:include schemaLocation="StatusType.xsd"/>
<xs:include schemaLocation="Document.xsd"/>
================ -->
<xs:element name="CFSListRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="RelativePath" type="xs:string"/>
<xs:element minOccurs="0" name="IncludeSubDir" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:simpleType name="EntryType">
<xs:restriction base="xs:string">
<xs:enumeration value="file"/>
<xs:enumeration value="directory"/>
</xs:restriction>
</xs:simpleType>
<xs:element name="CFSListResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
<xs:element maxOccurs="unbounded" minOccurs="0" name="DirectoryEntry" type="xoa:DirectoryEntryType">
<xs:annotation>
<xs:documentation>content of
DirectoryEntry is path relative to
the RelativePath</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:complexType name="DirectoryEntryType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="type" type="xoa:EntryType" use="required"/>
<xs:attribute name="modified" type="xs:dateTime" use="optional"/>
<xs:attribute name="size" type="xs:integer" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<!-- includes for standalone validation
<xs:include schemaLocation="StatusType.xsd"/>
================ -->
<xs:element name="CFSRenameRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="OldRelativePath" type="xs:string"/>
<xs:element name="NewRelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CFSRenameResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="OldRelativePath" type="xs:string"/>
<xs:element minOccurs="0" name="NewRelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- includes for standalone validation
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
<xs:include schemaLocation="StatusType.xsd"/>
<xs:include schemaLocation="Document.xsd"/>
================ -->
<xs:element name="CFSUploadRequest">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element name="RelativePath" type="xs:string"/>
<xs:element name="FileData" type="xoa:DocDataType"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="CFSUploadResult">
<xs:complexType>
<xs:sequence>
<xs:element name="Status" type="xoa:StatusType"/>
<xs:element minOccurs="0" name="SubmitId" type="xs:string"/>
<xs:element minOccurs="0" name="RelativePath" type="xs:string"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<!-- ===============================
<xs:include schemaLocation="AddressType.xsd"/>
<xs:include schemaLocation="Document.xsd"/>
<xs:include schemaLocation="EncodableStringType.xsd"/>
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
<xs:include schemaLocation="StatusType.xsd"/>
=============================== -->
<!-- Type definitions -->
<!-- Phone element -->
<xs:element name="Phone">
<xs:simpleType>
<xs:restriction base="xs:string">
<!-- <xs:pattern value="[0-9+x\-() ]{5,20}"/> -->
</xs:restriction>
</xs:simpleType>
</xs:element>
<!-- Email element -->
<xs:element name="Email">
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:minLength value="2"/>
<!-- <xs:pattern value="[@]{1,64}@([@\.]{1,64}\.){1,10}[^@\.]{1,64}"/> -->
</xs:restriction>
</xs:simpleType>
</xs:element>
<!-- Eformat type -->
<xs:simpleType name="EformatType">
<xs:annotation>
<xs:documentation> Only used in messageREACH.
Indicates the preferred email format of the
message body the recipient will receive.
Leaving the field empty or setting it to
"default" will send a multipart message body
rather than just a single message body if
it would do so normally. </xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="text"/>
<xs:enumeration value="html"/>
<xs:enumeration value="htmllite"/>
<xs:enumeration value="default"/>
</xs:restriction>
</xs:simpleType>
<!-- insert list element -->
<xs:element name="InsertList">
<xs:complexType>
<xs:choice>
<xs:element maxOccurs="unbounded" name="Insert">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="number" type="xs:integer"/>
<xs:attribute name="b64charset" type="xs:string" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:choice>
</xs:complexType>
</xs:element>
<!-- extension element -->
<xs:complexType name="SegmentType">
<xs:choice>
<xs:element maxOccurs="unbounded" name="Property">
<xs:complexType>
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="name" type="xs:string"/>
<xs:attribute name="b64charset" type="xs:string" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
</xs:element>
</xs:choice>
<xs:attribute name="name" type="xs:string"/>
</xs:complexType>
<xs:element name="Extension">
<xs:complexType>
<xs:choice maxOccurs="unbounded">
<xs:element name="Segment" type="xoa:SegmentType"/>
</xs:choice>
</xs:complexType>
</xs:element>
<!-- field mapping type -->
<xs:complexType name="FieldMappingType">
<xs:annotation>
<xs:documentation> Describes the correspondence
between the segment/keyword pairs in the
XDDS header file and columns in a table. Only
two table formats currently supported: CSV
(comma-separated values) and XSL (Excel
spreadsheet). The mapping may go either
from field name to the segment/keyword pair
or vice versa. In both cases, the same
structure may be used. </xs:documentation>
</xs:annotation>
<xs:sequence>
<xs:element maxOccurs="unbounded" name="Map">
<xs:complexType>
<xs:sequence>
<xs:element name="FieldName" type="xs:string"/>
<xs:element minOccurs="0" name="SegmentName" type="xs:string"/>
<xs:element name="PropertyName" type="xs:string"/>
<xs:element minOccurs="0" name="IsBase64Encoded" type="xs:boolean"/>
</xs:sequence>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:complexType>
<!-- class definitions -->
<!-- delivery item base class -->
<xs:element abstract="true" name="DeliveryItem" type="xoa:DeliveryItemType"/>
<xs:complexType abstract="true" name="DeliveryItemType">
<xs:attribute name="ref" type="xs:string" use="optional"/>
<xs:attribute name="refb64" type="xs:string" use="optional"/>
</xs:complexType>
<!-- new branch -->
<!-- delivery item container class -->
<xs:element abstract="true" name="DeliveryItemContainer" type="xoa:DeliveryItemContainerType"/>
<xs:complexType abstract="true" name="DeliveryItemContainerType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemType"/>
</xs:complexContent>
</xs:complexType>
<!-- list delivery item class -->
<xs:element name="List" type="xoa:ListType"/>
<xs:complexType name="ListType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemContainerType">
<xs:sequence>
<xs:element name="Name" type="xs:string"/>
</xs:sequence>
<xs:attribute name="ownershipLevel" type="xoa:OwnershipLevelType"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- SmQuery delivery item class -->
<xs:element name="SmQuery" type="xoa:SmQueryType"/>
<xs:complexType name="SmQueryType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemContainerType">
<xs:sequence>
<xs:element name="Name" type="xs:string"/>
</xs:sequence>
<xs:attribute name="ownershipLevel" type="xoa:OwnershipLevelType"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- External table delivery item class -->
<!-- This includes CSV and XLS files -->
<xs:element name="Table" type="xoa:TableType"/>
<xs:complexType name="TableType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemContainerType">
<xs:sequence>
<xs:element minOccurs="0" name="FieldMapping" type="xoa:FieldMappingType"/>
<xs:choice>
<xs:element name="DocRef" type="xs:string"/>
<xs:element name="Document" type="xoa:DocumentType"/>
</xs:choice>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- new branch -->
<!-- delivery item simple class -->
<xs:element abstract="true" name="DeliveryItemSimple" type="xoa:DeliveryItemSimpleType"/>
<xs:complexType abstract="true" name="DeliveryItemSimpleType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemType">
<xs:sequence>
<xs:element minOccurs="0" name="Alternate">
<xs:complexType>
<xs:choice>
<xs:element ref="xoa:Fax"/>
<xs:element ref="xoa:Internet"/>
<xs:element ref="xoa:Voice"/>
<xs:element ref="xoa:Fod"/>
<xs:element ref="xoa:Mbox"/>
<xs:element ref="xoa:Sms"/>
<xs:element ref="xoa:Telex"/>
<xs:element ref="xoa:DeliveryItemGeneric"/>
</xs:choice>
</xs:complexType>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- mbox delivery item class -->
<xs:element name="Mbox" type="xoa:MboxType"/>
<xs:complexType name="MboxType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemSimpleType">
<xs:sequence>
<xs:element name="UserId" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- telex delivery item class -->
<xs:element name="Telex" type="xoa:TelexType"/>
<xs:complexType name="TelexType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemSimpleType">
<xs:sequence>
<xs:element name="Number" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- FOD delivery item class -->
<xs:element name="Fod" type="xoa:FodType"/>
<xs:complexType name="FodType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemSimpleType">
<xs:sequence>
<xs:element name="Address" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- SMS delivery item class -->
<xs:element name="Sms" type="xoa:SmsType"/>
<xs:complexType name="SmsType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemSimpleType">
<xs:sequence>
<xs:element ref="xoa:Phone"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- new branch -->
<!-- Complex delivery item class -->
<xs:element abstract="true" name="DeliveryItemComplex" type="xoa:DeliveryItemComplexType"/>
<xs:complexType abstract="true" name="DeliveryItemComplexType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemSimpleType">
<xs:sequence>
<xs:element minOccurs="0" ref="xoa:InsertList"/>
<xs:element minOccurs="0" ref="xoa:Extension"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- fax delivery item class -->
<xs:element name="Fax" type="xoa:FaxType"/>
<xs:complexType name="FaxType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemComplexType">
<xs:sequence>
<xs:element ref="xoa:Phone"/>
<xs:element minOccurs="0" name="Att" type="xoa:EncodableStringType"/>
<xs:element minOccurs="0" name="From" type="xoa:EncodableStringType"/>
<xs:element minOccurs="0" name="To" type="xoa:EncodableStringType"/>
<xs:element minOccurs="0" name="Salutation" type="xs:string"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- voice delivery item class -->
<xs:element name="Voice" type="xoa:VoiceType"/>
<xs:complexType name="VoiceType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemComplexType">
<xs:sequence>
<xs:element ref="xoa:Phone"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- internet delivery item class -->
<xs:element name="Internet" type="xoa:InternetType"/>
<xs:complexType name="InternetType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemComplexType">
<xs:sequence>
<xs:element ref="xoa:Email"/>
<xs:element minOccurs="0" name="Subject" type="xoa:EncodableStringType"/>
<xs:element minOccurs="0" name="From" type="xoa:EncodableStringType"/>
<xs:element minOccurs="0" name="Eformat" type="xoa:EformatType"/>
<xs:element minOccurs="0" name="Password" type="xs:string">
<xs:annotation>
<xs:documentation> Only used in
messageREACH. The password used
by this recipient to retrieve
pull attachments. </xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- fax delivery item class -->
<xs:element name="DeliveryItemGeneric" type="xoa:DeliveryItemGenericType"/>
<xs:complexType name="DeliveryItemGenericType">
<xs:complexContent>
<xs:extension base="xoa:DeliveryItemComplexType">
<xs:sequence>
<xs:element name="Address" type="xs:string"/>
</xs:sequence>
<xs:attribute name="type" type="xoa:AddressType" use="required"/>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<!-- Finally, delivery item list -->
<!-- delivery item list type -->
<xs:complexType name="DeliveryItemListType">
<xs:choice maxOccurs="unbounded">
<xs:element ref="xoa:List"/>
<xs:element ref="xoa:SmQuery"/>
<xs:element ref="xoa:Table"/>
<xs:element ref="xoa:DeliveryItemGeneric"/>
<xs:element ref="xoa:Fax"/>
<xs:element ref="xoa:Internet"/>
<xs:element ref="xoa:Voice"/>
<xs:element ref="xoa:Fod"/>
<xs:element ref="xoa:Mbox"/>
<xs:element ref="xoa:Sms"/>
<xs:element ref="xoa:Telex"/>
</xs:choice>
</xs:complexType>
<!--remove includes later
<xs:include schemaLocation="AddressType.xsd"/>
================ -->
<xs:complexType name="DestinationType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="type" type="xoa:AddressType"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<!-- ===============================
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
=============================== -->
<!-- Elementary definitions go first -->
<xs:element name="CharacterSet" type="xs:string">
<xs:annotation>
<xs:documentation>use ISO names</xs:documentation>
</xs:annotation>
</xs:element>
<!-- Document type -->
<xs:simpleType name="DocFormatType">
<xs:restriction base="xs:string">
<xs:enumeration value="text"/>
<xs:enumeration value="XMF"/>
<xs:enumeration value="TIFF"/>
<xs:enumeration value="XAR"/>
<xs:enumeration value="PS"/>
<xs:enumeration value="PCL"/>
<xs:enumeration value="PDF"/>
<xs:enumeration value="MSW"/>
<xs:enumeration value="WAV"/>
<xs:enumeration value="RTF"/>
<xs:enumeration value="XLS"/>
<xs:enumeration value="HTML"/>
<xs:enumeration value="HTMLLITE"/>
<xs:enumeration value="unspec"/>
<xs:enumeration value="GIF"/>
<xs:enumeration value="JPEG"/>
<xs:enumeration value="PPT"/>
<xs:enumeration value="BMP"/>
<xs:enumeration value="VSD"/>
<xs:enumeration value="PUB"/>
<xs:enumeration value="MPP"/>
<xs:enumeration value="empty"/>
<!-- We do not need to know the document type for the -->
<!-- email attachments. -->
</xs:restriction>
</xs:simpleType>
<!-- Document Encoding format -->
<xs:simpleType name="DocEncodingFormat">
<xs:restriction base="xs:string">
<xs:enumeration value="text"/>
<xs:enumeration value="base64"/>
</xs:restriction>
</xs:simpleType>
<!-- Document embedded into the request -->
<xs:complexType name="DocDataType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="format" type="xoa:DocEncodingFormat" use="required"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<!-- All supported stored object types -->
<xs:simpleType name="SosObjectType">
<xs:restriction base="xs:string">
<xs:enumeration value="tts"/>
<xs:enumeration value="vcs"/>
</xs:restriction>
</xs:simpleType>
<!-- The types of the sos stored objects -->
<xs:complexType name="SosObjectIdType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="sosType" type="xoa:SosObjectType" use="required"/>
<xs:attribute name="ownershipLevel" type="xoa:OwnershipLevelType"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<!-- Another Document type -->
<xs:complexType name="DocumentType">
<xs:sequence>
<xs:element name="DocType" type="xoa:DocFormatType"/>
<xs:element minOccurs="0" name="Filename" type="xs:string"/>
<xs:choice>
<xs:element name="DocData" type="xoa:DocDataType"/>
<xs:element name="DocCfs" type="xs:string"/>
<xs:element name="DocUrl" type="xs:anyURI"/>
<xs:element name="SosObject" type="xoa:SosObjectIdType"/>
</xs:choice>
<xs:element minOccurs="0" ref="xoa:CharacterSet"/>
</xs:sequence>
<xs:attribute name="ref" type="xs:string" use="optional"/>
</xs:complexType>
<!-- The document set type -->
<xs:complexType name="DocumentSetType">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="Document" type="xoa:DocumentType"/>
</xs:sequence>
</xs:complexType>
<!-- The document by value or by reference -->
<xs:complexType name="DocumentOrRefType">
<xs:choice>
<xs:element name="DocRef" type="xs:string">
<xs:annotation>
<xs:documentation>must refer to a document
in document_set</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="Document" type="xoa:DocumentType"/>
</xs:choice>
</xs:complexType>
<xs:complexType name="EncodableStringType">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute name="b64charset" type="xs:string" use="optional"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<!--includes for standalone validation
================ -->
<xs:simpleType name="HistoryActionType">
<xs:restriction base="xs:string">
<xs:enumeration value="inserted"/>
<xs:enumeration value="updated"/>
<xs:enumeration value="deleted"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="ItemCountType">
<xs:simpleContent>
<xs:extension base="xs:integer">
<xs:attribute name="type" type="xoa:HistoryActionType"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:complexType name="HistoryType">
<xs:sequence>
<xs:element name="Action" type="xs:string"/>
<xs:element name="Operator" type="xs:string"/>
<xs:element name="Agent" type="xs:string"/>
<xs:element name="Time" type="xs:dateTime"/>
<xs:element name="ItemCount" type="xoa:ItemCountType"/>
</xs:sequence>
</xs:complexType>
<!-- ================
<xs:include schemaLocation="AddressType.xsd"/>
<xs:include schemaLocation="DestinationType.xsd"/>
<xs:include schemaLocation="Document.xsd"/>
<xs:include schemaLocation="JobIdType.xsd"/>
<xs:include schemaLocation="OwnershipLevelType.xsd"/>
<xs:include schemaLocation="StatusType.xsd"/>
<xs:include schemaLocation="RecStatusType.xsd"/>
================ -->
<xs:simpleType name="JobCancelType">
<xs:annotation>
<xs:documentation>The set of cancellation types/options</xs:documentation>
</xs:annotation>
<xs:restriction base="xs:string">
<xs:enumeration value="All"/>
<xs:enumeration value="Deliveries"/>
<xs:enumeration value="Reports"/>
<xs:enumeration value="AcceptanceReport"/>
<xs:enumeration value="CancellationNotice"/>
<xs:enumeration value="Pulls"/>
<xs:enumeration value="FriendDeliveries"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType name="JobCancelItemType">
<xs:sequence>
<xs:element name="JobId" type="xoa:JobIdType">
<xs:annotation>
<xs:documentation>requested JobId</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element minOccurs="0" name="CancelType" type="xoa:JobCancelType"/>
<xs:element minOccurs="0" name="NotificationAddress" type="xoa:DestinationType"/>
<xs:choice minOccurs="0">
<xs:element name="NotificationType" type="xs:string"/>
<xs:element name="NotificationText" type="xoa:DocDataType"/>
</xs:choice>
</xs:sequence>
</xs:complexType>
&Hi,
Not all data types from WSDL are supported during import. There is SAP Note about it.
please read it:
/people/kevin.liu/blog/2005/10/07/a-note-on-wsdl-and-xsd-imports--part-ii
regards,
wojtek
Message was edited by: Wojciech Gasiorowski
Maybe you are looking for
-
Problem with deploying j2ee app to weblogic server
I would like to deploy a j2ee application, that was successfully deploy on the iAS version 10.1.3, on to the web logic server. It deploy successfully, but when I try to run it, I get a 404 error. I can see in the web center, the application is up. Wh
-
NetPoint 5.9 - How to add multiple Customers to Campaign Contact List
Is there any ASP customisartion that can be done for NetPoint 5.9 CRM which would allow assigning of Multiple Sales persons to Accounts? If so please need help with the ASP code.
-
HT1414 Restored iphone now not syncing or backing up...
I have restored my iphone to delete all data, as I had issues with backing up, just taking extremely long more that 8 hours not normal. So restored my iphone and not it is still not backing up or syncing even when I selected the create new iphone. HE
-
Hi, Can anyone Please guide how to use input forms in BPC NW 10.0 when the requirement is to fetch the data by selecting the dimension member from input form and on the basis of that all the other dimension members gets select automatically and fetch
-
Top of the screen not touch sensitive sometimes.
I bought a brand new razr maxx 2 weeks ago. Right after I got it I found that periodically the top of the screen would not be touch sensitive. I would not be able to pull down the notification panel or click on buttons in apps where the button was