on 05-29-2007 5:15 AM
Hello,
Can someone please explain <xsd:include> tag with example??
Also specify the constraints regarding the usage of the same.
Thanx.
You are not supposed to use XSD include while designing data types/ msg types for using it in XI.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Let me explain what am i trying to do.....
I have created one "Address.xsd" and one "vendor.xsd".
But in Vendor.xsd file i want to include "address.xsd" file using <include> tag.
now these two xsd files need to be imported into XI under "External Definations".
So can i use <include> tag into these xsd file??
If Yes, How??
Am not sure. Just try this.
Delete both the imported XSDs. First import the vedor xsd and then improt the address xsd. The link I guess should be automatically established.
BTW, if you can give the XSD, I can give it a try from my system. You can find my mail id in my business card.
Regards,
Jai Shankar
Message was edited by:
Jai Shankar
Bhavesh,
Quote from SAP help
Procedure
1. To import a data type from an XSD file to the Integration Repository, you must first check whether the XSD file contains more than one global data type definition. You must only import one definition in each import.
2. Use the Integration Builder to create a data type with the same name as the data type to be imported from the XSD file. If there is a targetNamespace in the XSD file, it must correspond to the Repository namespace where you are creating this data type.
3. Choose Tools ® Import XSD and select an XSD file from the dialog that follows.
If there are other global data type definitions in the file, the processing log reports that data type definitions have been ignored.
4. If the imported data type contains references to other data types, these are displayed in a message. To import these data types, repeat the procedure in the previous two steps
Here these steps are not included. Hence assumed the link is established automatically.
Regards,
Jai Shankar
Hi anisha Sarode,
This design approach is the mirror image of the first approach:
<?xml version="1.0"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://www.library.org"
xmlns="http://www.library.org"
elementFormDefault="qualified">
<b><xsd:include schemaLocation="Book.xsd"/></b>
<xsd:element name="Library">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="BookCatalogue">
<xsd:complexType>
<xsd:sequence>
<xsd:element ref="Book"
maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
</xsd:schema>
with regards
Pradeep N
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.