| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WBIMB 5 - XML/mxsd errors |
« View previous topic :: View next topic » |
| Author |
Message
|
| dmj |
 Posted: Tue Oct 07, 2003 10:03 am Post subject: WBIMB 5 - XML/mxsd errors |
 |
|
Novice
Joined: 09 Apr 2002
Posts: 19
Location: London
|
I am having problems with creating an mxsd file from an imported schema.
The following are the steps I took and the files used.
Any help would be appreciated.
Thanks
Dj
----
Steps
Imported all xsd files associated with ct.xsd
Validated ct.xsd using WBIMB - no errors
New Message Definition file for global element ctmsg
Error message
Type 'ctmsg' has an unresolved base type http://xml.nr.co.uk/ns/2003/EAI#Message'
----------
Schema details
The imported schema has a multiple levels with the following structure.
Ct.xsd
No target namespace (imported into namespace itm)
Imports eai.xsd
Global element ctmsg
Eai.xsd
Namespace = http://xml.nr.co.uk/ns/2003/EAI
Includes msg.xsd
msg.xsd
no target namespace
imports nr_2003.xsd
global element Message + others
nr_2003.xsd
Namespace = http://xml.nr.co.uk/ns/2003/NR
Includes nr_types
Only contains the include
Nr_types.xsd
No target namespace
Contains simple types |
|
| Back to top |
|
 |
| kimbert |
| Posted: Wed Oct 08, 2003 4:20 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
I think I've seen this one...
When xsd files get imported into the 5.0 tooling, the directory structure is changed to match the namespace of each file.
e.g. if you import Eai.xsd which has Namespace = http://xml.nr.co.uk/ns/2003/EAI , it will be put into a directory <Message Set Root Directory>/xml/nr/co/uk/2003/EAI
To compensate for this, all <import> and <include> tags are rewritten to point at the correct location. If the imported xsd has no target namespace, it will always be put into <Message Set Root Directory>.
A problem arises when some of the imported schemas <include> noTargetNamespace schemas - the <include> tag does not always get rewritten correctly in this scenario, leading to the task list error which you are seeing.
There's a simple fix -
1. Open the mxsd file(s) which exhibit the problem
2. In the Outline view (lower left), select the root node.
3. Go to the Properties view (upper right), and you should see a list of imports and includes for the mxsd.
4. Delete (right-click and select 'Delete') each erroneous include, and replace it with a correct one (right-click 'Includes' and select 'Add Include').
5. Rebuild the project by selecting menu option 'Rebuild project', with the project root node highlighted in the Resource Navigator (upper left). |
|
| Back to top |
|
|
| dmj |
| Posted: Wed Oct 08, 2003 7:39 am Post subject: |
|
|
Novice
Joined: 09 Apr 2002
Posts: 19
Location: London
|
kimbert,
Thanks very much, worked brilliantly. Now might give some thought as to whether no target namespace is a good idea.
Cheers
DJ  |
|
| 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
|
|
|
|
