| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Unable to import XSD |
« View previous topic :: View next topic » |
| Author |
Message
|
| protocol |
 Posted: Thu Sep 08, 2005 3:16 pm Post subject: Unable to import XSD |
 |
|
Apprentice
Joined: 25 Feb 2005
Posts: 41
|
Hi All,
I am trying to create a .mxsd using a .xsd. When I try to create the message definition file from the XML Schema file, the following is the message i am getting :
Schema cannot be imported because it has the following unsupported features:
Definition ......... contains a Union , which is not supported.
I am using WBIMB v5.0.6.
How do i resolve this ? |
|
| Back to top |
|
 |
| JT |
| Posted: Thu Sep 08, 2005 7:19 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
| How do i resolve this ? |
By reading the documentation:
http://publib.boulder.ibm.com/infocenter/wbihelp/topic/com.ibm.etools.mft.doc/ad15870_.htm
http://publib.boulder.ibm.com/infocenter/wbihelp/topic/com.ibm.etools.mft.doc/ad15830_.htm
| Quote: |
Message sets without namespace support
Constructs not accepted as they stand when importing an XML schema.
When importing an XML Schema into a message set that does not support namespaces, the following constructs are not accepted as they stand: - Redefine
- Import
- List
- Union
- Abstract complex type
- Abstract element
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:
Redefine statements are ignored and not imported.
Import statements are replaced with include statements.
Any list/union types are modified to be a restriction with a base type xsd:string.
Abstract complex types are changed into non-abstract complex types.
Abstract elements are changed into non abstract elements.
Note that these modifications are the equivalent modifications that were performed by the WMQI 2.1 XML Schema importer command, for compatibility. |
|
|
| Back to top |
|
|
| protocol |
| Posted: Thu Sep 08, 2005 8:13 pm Post subject: |
|
|
Apprentice
Joined: 25 Feb 2005
Posts: 41
|
Hi JT,
Thanks for your reply. My message set is using namespaces and according to the documentation, the xsd cannot have Unions in it.
Is this something that might be fixed in the future ?
What would be the solution to my problem ? How do i create a mxsd from this xsd ? I am not sure if I can modify the xsd's so that they do not have the Union declarations. |
|
| Back to top |
|
|
| MiLi |
| Posted: Fri Oct 07, 2005 4:08 am Post subject: Its fixed in wbimb 6 |
|
|
Acolyte
Joined: 07 Oct 2005
Posts: 51
|
Hi
Its been fixed in version 6 |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Oct 07, 2005 4:31 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
I can confirm that union simple types are supported in v6.0, but not in v5.
| Quote: |
| I am not sure if I can modify the xsd's |
You don't have to modify the original XSDs. You could take a copy, and modify the copy. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
