| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Add xml format to imported cobol msg set |
« View previous topic :: View next topic » |
| Author |
Message
|
| MiLi |
 Posted: Mon Jan 30, 2006 6:16 am Post subject: Add xml format to imported cobol msg set |
 |
|
Acolyte
Joined: 07 Oct 2005
Posts: 51
|
Hi
I'm having a card time adding a xml namespace format to my message set.
first I created my message set with the "use namespaces" option.
Then I created the Message definition file from a cobol copy.
Now I want to add a xml format with a target namespace.
I can add a namespace declaration in my .mset file but it will only reult in :
<msg_Message xmlns:xmlns="http://mynamespace" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<test>dtest</test>
</msg_Message>
In my .mxsd file, all namespace are empty and grey.
Is it possible to add a xml format with a namespace, to an exising cwf message set?
_________________
IBM Certified System Administrator - WebSphere MQ V6.0
IBM Instructor - WebSphere MQ, WebSphere Message Broker |
|
| Back to top |
|
 |
| kimbert |
| Posted: Mon Jan 30, 2006 9:05 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
This is a known limitation in v5. The v6 COBOL importer allows you to specify a target namespace for the mxsd files it creates. Since you don't have this feature, you'll need a workaround.
- Do the steps which you have already described
- Create another message definition file with your desired target namespace.
- Go to the properties of the new message definition file, and include ( not import ) the COBOL-imported message definition file.
- If, when you imported the copybook, you selected some global elements to be messages THEN for each such message, create an alias which has a namespace. To do this, create new messages based on the global elements in the imported mxsd file.
That last step will mean that you have two copies of each message - one created by the COBOL importer one created by you. You could avoid this by not choosing any global elements during the COBOL import.
To find the import/include settings for a .mxsd file , open the mxsd file and select the root node in the Outline view.
In case you're wondering, this workaround relies on the 'chameleon namespace' feature of XML Schema. The included content automatically takes on the target namespace of the including schema. |
|
| 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
|
|
|
|
