External definition, dtd references
Hi,
My openTRANS_ORDER_1_0.dtd is refering to "openbase_1_0.dtd
When I create the external definition both dtds is imported
openTRANS_ORDER_1_0_dtd
openbase_1_0_dtd
openTRANS_ORDER_1_0.dtd has a External reference :
Source: openbase_1_0.dtd
Name: openbase_1_0_dtd
and openbase_1_0_dtd has also filled out the
Source : openbase_1_0_dtd
So the dtd reference should be OK now !
But when I try to create the Message Interfaces it is not possible to choose
Any Elements under the external definition openTRANS_ORDER_1_0_dtd.
I would expect to could choose the ORDER element
Here is the openTRANS_ORDER_1_0.dtd.:
<!ENTITY % OPENBASE SYSTEM "openbase_1_0.dtd">
%OPENBASE;
<!ELEMENT ORDER (ORDER_HEADER, ORDER_ITEM_LIST, ORDER_SUMMARY)>
<!ATTLIST ORDER....."standard">
<!ELEMENT ORDER_HEADER (CONTROL_INFO?, SOURCING_INFO?, ORDER_INFO)>
<!ELEMENT ORDER_INFO (ORDER_ID, ALT_CUSTOMER_ORDER_ID*, ORDER_DATE, ...)>
<!ELEMENT ORDER_ITEM_LIST (ORDER_ITEM)>
<!ELEMENT ORDER_SUMMARY (TOTAL_ITEM_NUM, TOTAL_AMOUNT?)>
Can any one explain why I cannot choose any elements when creating my message definition !
Frank
u will be able to choose only the message type in the message interface and not the elements of the message type in message interface.
Similar Messages
-
Import SAP WSDL into External Definition
Hi Friends,
I'd like to import a WSDL into XI External Definition. However, the WSDL is gained from Web AS Web Service Navigator. So it is a zip file and consists of three WSDL files. How can I import them into the external definition?
Thanks + Regards
JeromeHi Jerome,
If you have three wsld files then aren't those three messages?
have you tried importing them as external definitions one by one?
you can check how the message structre looks like
when you try to use the external definition inside a
message mapping (remember you don't create message type from external definitions)
Futher reference:
http://help.sap.com/saphelp_nw04/helpdata/en/26/9e97b0f525d743882936c2d6f375c7/content.htm
BTW
while creating external defnitions (WSDL)
you can only choose wsld file or XML - nothing else
Regards,
michal -
DTD files as external Definition
Hi ,
Read lot of threads on this which are having same problem ,some of them got solved none of them posted how did they succeded on those.
i am getting error like Name "ds:Signature" is incorrect, when i tried to inport the .dtd file as external definition,so I did try converting dtd file to XSD ,it is creating the 3 xsd files and none of them are valid each one of them are error.But however the DTD file is valid .
Using Invoicedetail DTD file for my scenario.
you can download the file from http://cxml.org
Please let me knw on this.
Thanks,
MadhuHi,
Here are the errors for the 3 xsd's
1. Value 'ds:Signature' is not allowed for attribute 'ref'.
Hint: A valid value would be 'xml:lang'.
Error location: xs:schema / xs:element / xs:complexType / xs:sequence / xs:element / @ref
2. Value 'ds:Signature' is not allowed for attribute 'ref'.
Hint: A valid value would be 'xml:lang'.
Error location: xs:schema / xs:element / xs:complexType / xs:sequence / xs:element / @ref
3. Value 'xades:Identifier' is not allowed for attribute 'ref'.
Hint: A valid value would be 'xml:lang'.
Error location: xs:schema / xs:element / xs:complexType / xs:sequence / xs:element / @ref
these errors are coming in xml spy when i tried to validate .
Thanks,
Madhu
Edited by: madhu204 on Jul 23, 2009 4:54 PM
Edited by: madhu204 on Jul 23, 2009 4:55 PM -
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. -
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 -
Dom can't parse dtd reference in xml file
Hi all,
I am trying to parse a xml file (hibernate mapping file *.hbm.xml) using DOM. But itis getting timeout errorwhile parsing due to the external dtd reference in the xml file.
<!DOCTYPE hibernate-mapping PUBLIC
"-//Hibernate/Hibernate Mapping DTD//EN"
"http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd" >I understand that the program is trying to access the document and is not being able to do so. But I don't have any clue to solve this problem. I don't want to remove the reference from the xml file.
The following method is trying to parse the xml file:
public void parseXML(String file) {
factory = DocumentBuilderFactory.newInstance();
System.out.println(file);
try {
builder = factory.newDocumentBuilder();
document = builder.parse(file);
Element docEle = document.getDocumentElement();
NodeList n1 = docEle.getElementsByTagName("class");
for(int i = 0; i < n1.getLength(); i++) {
Element e1 = (Element) n1.item(i);
String nm = e1.getAttribute("name");
System.out.println(nm);
} catch(Exception e) {
throw new RuntimeException(e);
}Please help me on this....I am at no end....Please let me know if there is any method so that the parser will overlook this reference and will parse the xml file....or any other sort of solution....
Thanks in advance...
AnirCan you provide a working sample? Upload to Onedrive and share it with us.
Matt Small - Microsoft Escalation Engineer - Forum Moderator
If my reply answers your question, please mark this post as answered.
NOTE: If I ask for code, please provide something that I can drop directly into a project and run (including XAML), or an actual application project. I'm trying to help a lot of people, so I don't have time to figure out weird snippets with undefined
objects and unknown namespaces. -
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 -
Scenario proxy to soap synchronous with external definitions
Hi all,
I have a problem with my scenario.
In development environment all is working fine, but when I have transported to preproduction environment and we have executed my scenario I have the following error:
<SAP:AdditionalText>com.sap.engine.interfaces.messaging.api.exception.MessagingException: SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server did not recognize the value of HTTP Header SOAPAction: http://geisiedes.endesa.es/WSRespuesta/WsRespuestaSIE.asmx/EnviarRespuestaNocturnaWF.</SAP:AdditionalText>
<SAP:Stack />
I attach the receiver communication channel configuration.(cc_config.jpg)
I changed the target URL in the receiver channel, with the preproduction machine, but I didn't change the sopa action because is define in the wsdl ( soap_action.jpg).
I have othe external definitions for preproduction environmet but its contect is different to external definitions in development change the reference to machine where geisiepre instead geiseides.
Whe I import this external definitions I lose the configuration in messages mappings.
How can I solve this problem? Is mandatory to have the same external definitions in the three environments??
Thanks and best regards
MónicaHi Monica,
I normally use the all the tag content in the SOAPAction tag, but you can try with EnviarRespuestaNocturnaPC in the SOAP receiver communication channel.
Have you tried to test your wsdl endpoint with SOAPui?, you can get sometimes valuable information about how design/configure in PI and if the request is identical in PI and in SOAPui.
Regards. -
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 -
External definitions import into Message mapping
Hi,
I have a DTD message in external definitions to be imported into the message mapping. But I am not able to choose the object in the mapping editor. It does not allow even if the message is a valid WSDL. The only time it allows to import into the message editor is when its an XSD.I am not sure why the external definitions in DTD or WSDL formats are not able to be imported or am I missing something??
-KenHi,
A conversion of the downloaded cXML DTD into XSD by using XMLSPY yields 3 XSD files. Using the initial XSD(which has the major fields) yields the same error(i.e cannot create messages or valid WSDL) in external definitions.
I also tried using one of the standard xml's from the cXML site and the funny part was XMLSPY validated them without errors and while importing them directly into the mapping editor, XI throws an error "XML NOT WELL FORMED". Its so weird.
Also is there a possibility to write a script to manipulate the payload message after passing through the adapters? For eg : Creating a script which will delete a valid tag in payload before it reaches the 3rd party. ...By adding the DOCTYPE in the prolog, the message would look like this :
"<?xml...utf-8>
<!DOCTYPE......'Cxml.org'>
<?xml.....utf-8>
<start tag></start tag>
Therefore some kind of a script that would remove the second <?xml tag on line 3>..
This is just a round about thinking
Any ideas.. -
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 -
Hi Friends,
There is a requirement for external definition to import. I got one file from client text file having xml data. So i have save as to .XSD format and tested in XI while uploading into external definitions.
As per my knowledge, .XSD/wsdl/dtd file can be used for external definitions. And, it acts as Message type so create MI .
So , if we request from client , is there specific format is there for .XSD??? Is it only message type else data type possible ???
How to guide the client to get the .XSD files?
Thank you
DevaHi Deva,
first convert XML file in to XSD,for that you can use XML Editors ALTOVA XML Spy or Styalus studio to conver XML to XSD.
you can get free trail versions available.
The XML to XSD conversion process very easy , just google it.
if you have XSD then you no need to create Data type and Message Type.
Regards,
Raj -
External definition and used them as Data Type Templates
hi all
how to Develop external definition and used them as Data Type Templates .
Thank u
SwariHI
External Definitions: If a definition of the message structure exists in wsdl, xsd, dtd formats, we can use it in the integration repository by importing it as an external definition.
External Definations:
An external definition enables you to import a local WSDL, XSD, or DTD file to the Integration Repository and specify which parts of the schema to extract as the description for a message. You can use these extracted message schema as:
Output or input messages in message interfaces
Source or target structures for message mappings
There is a series of standard schema for describing the message structure at runtime. WSDL (Web Service Description Language), XSD (XML Schema Definition Language), or DTDs (Document Type Definitions) are often used to describe message schema. If a description of the message structure already exists in one of the above formats, you can use it in the Integration Repository by importing it as an external definition rather than re-entering it manually using the data type editor.
Have a look at
http://help.sap.com/saphelp_nw04/helpdata/en/43/ce49ef1019087ae10000000a1553f6/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ba/d4c23b95c8466ce10000000a114084/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/26/9e97b0f525d743882936c2d6f375c7/content.htm
cheers -
XSDBuilder fails to resolve DTD references
I am evaluating XDK 9.2.0.5.0 for Java and have encountered a problem
with XML Schema support.
I am using XSDBuilder to build an XMLSchema object from several .xsd
files. The main .xsd file is secext.xsd, and this file imports other
.xsd files. I assign an EntityResolver to the XSDBuilder so that all
imported schema files will be read from my local file system, rather
than being retrieved from the Internet.
XSDBuilder does call my EntityResolver to resolve the import
statements in the XML Schema files; however, it fails to call my
EntityResolver to resolve XMLSchema.dtd reference in the DOCTYPE
declaration of xml.xsd.
I am using Oracle XDK version 9.2.0.5.0 on Solaris 8 with Java 1.4. I
have also tried version 10.1.0.0.0 beta and received the same results.
Here is the test case:
Download the following files and save them in /tmp/xsd/.
http://schemas.xmlsoap.org/ws/2002/04/secext/secext.xsd
http://www.w3.org/2001/xml.xsd
http://www.w3.org/TR/xmldsig-core/xmldsig-core-schema.xsd
http://www.w3.org/2001/XMLSchema.dtd
Compile and run OracleSchemaTest.java, passing 'secext.xsd' as the
command line arg.
java dfranklin.OracleSchemaTest secext.xsd
It produces the following output:
resolveEntity: null, secext.xsd
resolved to /tmp/xsd/secext.xsd
resolveEntity: http://schemas.xmlsoap.org/ws/2002/04/secext, http://www.w3.org/2001/xml.xsd
resolved to /tmp/xsd/xml.xsd
<Line 2, Column 80>: XML-0112: (Fatal Error) Error opening external DTD 'XMLSchema.dtd'.
Exception in thread "main" oracle.xml.parser.schema.XSDException: Error opening external DTD 'XMLSchema.dtd'.
at oracle.xml.parser.schema.XSDBuilder.parseIncludeAndImport(XSDBuilder.java:814)
at oracle.xml.parser.schema.XSDBuilder.parseTopLevelElem(XSDBuilder.java:662)
at oracle.xml.parser.schema.XSDBuilder.buildSchema(XSDBuilder.java:486)
at oracle.xml.parser.schema.XSDBuilder.build(XSDBuilder.java:304)
at oracle.xml.parser.schema.XSDBuilder.build(XSDBuilder.java:249)
at dfranklin.OracleSchemaTest.buildXMLSchema(OracleSchemaTest.java:48)
at dfranklin.OracleSchemaTest.run(OracleSchemaTest.java:29)
at dfranklin.OracleSchemaTest.main(OracleSchemaTest.java:23)
The output shows that the EntityResolver is not being called to
resolve 'XMLSchema.dtd'.
=== begin OracleSchemaTest.java ===
package dfranklin;
import java.io.FileInputStream;
import java.io.FileNotFoundException;
import java.io.IOException;
import java.io.InputStream;
import oracle.xml.parser.schema.XMLSchema;
import oracle.xml.parser.schema.XSDBuilder;
import oracle.xml.parser.schema.XSDException;
import oracle.xml.parser.v2.XMLError;
import org.xml.sax.InputSource;
public class OracleSchemaTest
implements org.xml.sax.EntityResolver
private static String xsdstr;
private static String basepath = "/tmp/xsd";
public static void main(String[] args)
throws Exception
xsdstr = args[0];
new OracleSchemaTest().run();
public void run()
throws Exception
XMLSchema xmlSchema = buildXMLSchema(xsdstr);
System.out.println("xmlSchema=" + xmlSchema);
public XMLSchema buildXMLSchema(String systemId)
throws Exception
XSDBuilder xsdBuilder = new XSDBuilder();
xsdBuilder.setEntityResolver(this);
InputStream xsdin = null;
InputSource insrc = resolveEntity(null, xsdstr);
if (insrc != null) {
xsdin = insrc.getByteStream();
if (xsdin == null) {
throw new IOException("Can't resolve entity " + xsdstr);
XMLSchema xmlSchema = (XMLSchema)xsdBuilder.build(xsdin, null);
return xmlSchema;
public InputSource resolveEntity(String publicId, String systemId)
throws
org.xml.sax.SAXException,
java.io.IOException
System.err.println("resolveEntity: " + publicId + ", " + systemId);
String fn;
if ("http://www.w3.org/2001/xml.xsd".equals(systemId)) {
fn = basepath + "/" + "xml.xsd";
} else if ("http://www.w3.org/TR/xmldsig-core/xmldsig-core-schema.xsd".equals(systemId)) {
fn = basepath + "/" + "xmldsig-core-schema.xsd";
} else if ("http://www.w3.org/2001/XMLSchema.dtd".equals(systemId)) {
fn = basepath + "/" + "XMLSchema.dtd";
} else {
fn = basepath + "/" + systemId;
try {
InputStream in = new FileInputStream(fn);
System.err.println("resolved to " + fn);
InputSource insrc = new InputSource(in);
insrc.setSystemId(systemId);
return insrc;
} catch (FileNotFoundException e) {
return null;
==== end OracleSchemaTest.java ===I am evaluating XDK 9.2.0.5.0 for Java and have encountered a problem
with XML Schema support.
I am using XSDBuilder to build an XMLSchema object from several .xsd
files. The main .xsd file is secext.xsd, and this file imports other
.xsd files. I assign an EntityResolver to the XSDBuilder so that all
imported schema files will be read from my local file system, rather
than being retrieved from the Internet.
XSDBuilder does call my EntityResolver to resolve the import
statements in the XML Schema files; however, it fails to call my
EntityResolver to resolve XMLSchema.dtd reference in the DOCTYPE
declaration of xml.xsd.
I am using Oracle XDK version 9.2.0.5.0 on Solaris 8 with Java 1.4. I
have also tried version 10.1.0.0.0 beta and received the same results.
Here is the test case:
Download the following files and save them in /tmp/xsd/.
http://schemas.xmlsoap.org/ws/2002/04/secext/secext.xsd
http://www.w3.org/2001/xml.xsd
http://www.w3.org/TR/xmldsig-core/xmldsig-core-schema.xsd
http://www.w3.org/2001/XMLSchema.dtd
Compile and run OracleSchemaTest.java, passing 'secext.xsd' as the
command line arg.
java dfranklin.OracleSchemaTest secext.xsd
It produces the following output:
resolveEntity: null, secext.xsd
resolved to /tmp/xsd/secext.xsd
resolveEntity: http://schemas.xmlsoap.org/ws/2002/04/secext, http://www.w3.org/2001/xml.xsd
resolved to /tmp/xsd/xml.xsd
<Line 2, Column 80>: XML-0112: (Fatal Error) Error opening external DTD 'XMLSchema.dtd'.
Exception in thread "main" oracle.xml.parser.schema.XSDException: Error opening external DTD 'XMLSchema.dtd'.
at oracle.xml.parser.schema.XSDBuilder.parseIncludeAndImport(XSDBuilder.java:814)
at oracle.xml.parser.schema.XSDBuilder.parseTopLevelElem(XSDBuilder.java:662)
at oracle.xml.parser.schema.XSDBuilder.buildSchema(XSDBuilder.java:486)
at oracle.xml.parser.schema.XSDBuilder.build(XSDBuilder.java:304)
at oracle.xml.parser.schema.XSDBuilder.build(XSDBuilder.java:249)
at dfranklin.OracleSchemaTest.buildXMLSchema(OracleSchemaTest.java:48)
at dfranklin.OracleSchemaTest.run(OracleSchemaTest.java:29)
at dfranklin.OracleSchemaTest.main(OracleSchemaTest.java:23)
The output shows that the EntityResolver is not being called to
resolve 'XMLSchema.dtd'.
=== begin OracleSchemaTest.java ===
package dfranklin;
import java.io.FileInputStream;
import java.io.FileNotFoundException;
import java.io.IOException;
import java.io.InputStream;
import oracle.xml.parser.schema.XMLSchema;
import oracle.xml.parser.schema.XSDBuilder;
import oracle.xml.parser.schema.XSDException;
import oracle.xml.parser.v2.XMLError;
import org.xml.sax.InputSource;
public class OracleSchemaTest
implements org.xml.sax.EntityResolver
private static String xsdstr;
private static String basepath = "/tmp/xsd";
public static void main(String[] args)
throws Exception
xsdstr = args[0];
new OracleSchemaTest().run();
public void run()
throws Exception
XMLSchema xmlSchema = buildXMLSchema(xsdstr);
System.out.println("xmlSchema=" + xmlSchema);
public XMLSchema buildXMLSchema(String systemId)
throws Exception
XSDBuilder xsdBuilder = new XSDBuilder();
xsdBuilder.setEntityResolver(this);
InputStream xsdin = null;
InputSource insrc = resolveEntity(null, xsdstr);
if (insrc != null) {
xsdin = insrc.getByteStream();
if (xsdin == null) {
throw new IOException("Can't resolve entity " + xsdstr);
XMLSchema xmlSchema = (XMLSchema)xsdBuilder.build(xsdin, null);
return xmlSchema;
public InputSource resolveEntity(String publicId, String systemId)
throws
org.xml.sax.SAXException,
java.io.IOException
System.err.println("resolveEntity: " + publicId + ", " + systemId);
String fn;
if ("http://www.w3.org/2001/xml.xsd".equals(systemId)) {
fn = basepath + "/" + "xml.xsd";
} else if ("http://www.w3.org/TR/xmldsig-core/xmldsig-core-schema.xsd".equals(systemId)) {
fn = basepath + "/" + "xmldsig-core-schema.xsd";
} else if ("http://www.w3.org/2001/XMLSchema.dtd".equals(systemId)) {
fn = basepath + "/" + "XMLSchema.dtd";
} else {
fn = basepath + "/" + systemId;
try {
InputStream in = new FileInputStream(fn);
System.err.println("resolved to " + fn);
InputSource insrc = new InputSource(in);
insrc.setSystemId(systemId);
return insrc;
} catch (FileNotFoundException e) {
return null;
==== end OracleSchemaTest.java === -
Extenal Refence in External Definition
Hi,
I need to use an external WSDL as a External Definition. The WSDL contains this line:
<b><xsd:include schemaLocation="../service/FordringModtagSAP38Interface.xsd" /></b>
How do i import the includet schema? It´s not allowed to call it <b>../service</b>
How do i do it??
/JakobLet me try to explain it better.
Assume the XSD A refers to XSD B.
1. Import XSD A.
2. In XSD A ( the main XSD ), you will find a tab EXTERNAL REFERENCES . In this you should find an entry for Source. Copy this.
3. Import XSD B.
4. When you import, you will find a field called Source after you import it. Paste the Copied Text of step 2 here.
5. Save and activate.
6. Now, XSD A, in External References should contain both Name and Source filled.
Regards
Bhavesh
Maybe you are looking for
-
I need your help on an issue : A customer has the following Architecture : - Host Mahcine running on windows and where he have the CVI and CVI Real Time 8.5 - a PXI system with 8106 controller. They want to boot their PXI 8106 on RT so they bought th
-
Can one turn page for printing in Pages OS 6.8?
I am using Pages 09. The system on my iMac is 10.6.8. My seldom used small footprint printer can only print 8 1/2' wide. When selecting print, I find nothing which allows me to turn the page so that I can use an 11" envelope inserted lengthwise. Ha
-
I have a search page with a report region showing top 10 departments. The query I have used is : select deptno, count(empno) countv from emp WHERE rownum < 11 GROUP BY deptno order by deptno desc If the count = 1, then clicking on the column(link), I
-
How do I reclaim space after a spill
My SYSAUX tablespace have grown significantly becase of a spill. STREAMS$_APPLY_SPILL_MSGS_PART is pretty large. How do I clear this out ? Thanks
-
Procurement with account assignment category F
Hiiiiiiiiiiiiiiiiii Experts, I have a requirement.I am making a PO with account assignment category 'F'. There i am giving production order in account assignment tab of item in PO.Now after doing GRN with movement type 103 and QI with mov. type 105 i