| Author |
Message
|
| psn |
 Posted: Sun Nov 09, 2003 8:38 am Post subject: Messageset Migration WMQI 2.1 --> WBIMB 5.5 CSD01 |
 |
|
Disciple
Joined: 30 Oct 2002
Posts: 193
Location: France
|
Hi,
By migrate a Message Set from WMQI 2.1 to WBIMB 5.0 I
have the Following error in the Toolkit Task list:
"Kind Status Priority Description Resource In Folder Location
Error Element 'TYP' must not be rendered as an attribute when its
enclosing group is nested more than one level deep in complex type
't_VERSION_type'. Physical format: 'XML'. XXXX_Messages_01_02.mxsd
XXX_msgset/XXXX_Messages_02"
This TYP Element is an XML Attribut in the XML Message.
What does it mean exactly and how could I correct this Situation without modify the message structure ?
PSN |
|
| Back to top |
|
 |
| kimbert |
| Posted: Mon Nov 10, 2003 1:27 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Hi,
This is a known problem. Here's the readme entry for CSD2:
mqsimigratemsgsets command
If you are migrating a message set that was originally created by importing an XML DTD, or XML Schema, file under WebSphere MQ Integrator V2.1, you might find that the message set project contains task list errors of the following kind: "Element 'xxxx' must not be rendered as an attribute when its enclosing group is nested more than one level deep in complex type 'zzzz'."
This is caused by the way that the WebSphere MQ Integrator V2.1 importers created structures to hold XML attributes. A fix will be made available for this problem. In the meantime, you are recommended to use one of the following workarounds:
* Re-import the XML DTD, or XML Schema, file directly into the V5 Message Broker Toolkit ensuring that the message set has not specified the 'Use Namespaces' option.
* Using the Message Editor, for each such group of elements rendered as attributes, create the equivalent attribute group, ensuring that each new attribute has the same XML Wire Format properties as the corresponding original element. Then delete the group of elements and the reference to it from the complex type, and replace by a reference to the new attribute group.
[/b] |
|
| Back to top |
|
|
| psn |
| Posted: Tue Nov 11, 2003 3:12 am Post subject: |
|
|
Disciple
Joined: 30 Oct 2002
Posts: 193
Location: France
|
I have export the messageset as dtd from WMQI 2.1 and try to import them into WBIMB 5.0 . I have defined a new messageset project in the toolkit, right clic on the messageset name select new but I don't find Message Definition File Wizard...
Does it give anothe way to import a dtd in WBIMB 5.0
PSN |
|
| Back to top |
|
|
| psn |
| Posted: Tue Nov 11, 2003 4:02 am Post subject: |
|
|
Disciple
Joined: 30 Oct 2002
Posts: 193
Location: France
|
I have open windows-->preferences in the tool kit and under the messageset folder I have only editors but not XML Schema Importer
Why ?
Where cant I find the XML Schema Importer ?
How can I add this funktion in the tool kit ?
PSN |
|
| Back to top |
|
|
| psn |
| Posted: Thu Nov 13, 2003 3:06 am Post subject: |
|
|
Disciple
Joined: 30 Oct 2002
Posts: 193
Location: France
|
I had not delete the workspace after upgrade to CD02. now I can import dtd but I have more errors as after the migration.
PSN |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Nov 13, 2003 7:42 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
OK - I need to check the situation...
You can now create a message definition file, but you are getting the same error as before...or are the errors slightly different now?
Assuming that you are getting the same error, I think you need to follow the second option in the readme entry:
* Using the Message Editor, for each such group of elements rendered as attributes, create the equivalent attribute group, ensuring that each new attribute has the same XML Wire Format properties as the corresponding original element. Then delete the group of elements and the reference to it from the complex type, and replace by a reference to the new attribute group.
This will require you to modify your message definitions, but if you get it right, it will not affect the dictionary which is deployed to the broker. Let me know if you need help with understanding the instructions. |
|
| Back to top |
|
|
| psn |
| Posted: Fri Nov 14, 2003 12:57 am Post subject: |
|
|
Disciple
Joined: 30 Oct 2002
Posts: 193
Location: France
|
hi kimbert,
thanks for your help. Your workaround is fine. all is fine now !
PSN |
|
| Back to top |
|
|
|
|
