When importing an XML Schema into a message set that supports namespaces, the constructs below are not accepted. When the user tries to import a schema containing one or more of these constructs, an error is reported that indicates why and where the import fails.
The following is a list of these schema declarations:
The following is an example of each of these constructs:
<?xml version="1.0" encoding="UTF-8"?> <schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns:ibm="http://www.ibm.com"> <!-- Unsupported feature: redefine --> <redefine schemaLocation="test.xsd"/> <!-- Unsupported feature: list --> <simpleType name="type1"> <list itemType="string" /> </simpleType> <!-- Unsupported feature: union --> <simpleType name="type2"> <union memberTypes="string" /> </simpleType> </schema>
When importing an XML Schema into a message set that supports namespaces, the constructs below are accepted, but will be ignored and will not be deployed to the broker. When the user tries to import a schema containing one or more of these constructs, a warning is issued stating that they will be ignored. You will be able to delete these constructs, but there are no properties that can be configured for them.
If you extract the logical model for the message (for example using the Schema Generation facility) these constructs are ignored and are not included in the output schema.
The following is a list of these schema declarations:
The following is an example of each of these constructs:
<?xml version="1.0" encoding="UTF-8"?> <schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns:ibm="http://www.ibm.com"> <!-- Accepted feature: unique --> <element name="element1" type="string"> <unique name="unique1"> <selector xpath="path1"></selector> <field xpath="path1"></field> </unique> </element> <!-- Accepted feature: key --> <element name="element2" type="string"> <key name="key1"> <selector xpath="path1"></selector> <field xpath="path1"></field> </key> </element> <!-- Accepted feature: keyref --> <element name="element3" type="string"> <keyref name="keyref1" refer="ibm:key1"> <selector xpath="path1"></selector> <field xpath="path1"></field> </keyref> </element> </schema>
The problem occurs when an XML schema that has a target namespace, includes another XML schema that has no target namespace. The Schema Location created in the message model for the include just specifies the filename. This does not take into account that the including and included message definition files are in different directories within the message model.
You can fix problem from the workbench by selecting the Properties tab of the including message definition file in the Message Definition Editor. Delete the include entry with the incorrect Schema Location then add another include entry, selecting the correct file from the file menu.
When importing an XML Schema into a message set that does not support namespaces, the following constructs are not accepted as they stand:
The user has the choice to reject or modify these constructs based on the preferences set by the user in the XML Schema Importer preference page (or the mqsicreatemsgdefs import options file). If the user specifies "reject", when the construct is encountered, the import stops and an error is reported. If the user specifies "modify", when the construct is encountered, the importer modifies the resulting message definition file as follows:
Note that these modifications are the equivalent modifications that were performed by the WMQI 2.1 XML Schema importer command, for compatibility.
The following is an example of each of these constructs:
<?xml version="1.0" encoding="UTF-8"?> <schema xmlns="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns:ibm="http://www.ibm.com"> <!-- Unsupported feature: redefine --> <redefine schemaLocation="test.xsd"/> <!-- Unsupported feature: import --> <import schemaLocation="test1.xsd" namespace="http://www.ibm1.com"/> <!-- Unsupported feature: list --> <simpleType name="type1"> <list itemType="string" /> </simpleType> <!-- Unsupported feature: union --> <simpleType name="type2"> <union memberTypes="string" /> </simpleType> <!-- Unsupported feature: abstract complex type --> <complexType name="type3" abstract="true"></complexType> <!-- Unsupported feature: abstract element --> <element name="element" type="string" abstract="true"></element> </schema>
Unique, Key and Keyref constructs are imported and appear in the generated message definition file but, since these constructs are not supported, error task entries are created to inform the user that the generated .mxsd file has problems.
When importing an XML schema into a message set that does not support namespaces, you cannot import a schema document that has a target namespace that is not qualified with a prefix. For example:
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.ibm.com" xmlns="http://www.ibm.com"> </xsd:schema>
Related concepts
Message modeling
The message model
Related tasks
Developing message models
Working with a message definition file
Working with message model objects
Importing
Related reference
Message model reference information
Message model object properties
Import formats
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ad15870_ |