ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » WMQI 2.1.9 Message Set Migration Issue

Post new topic  Reply to topic
 WMQI 2.1.9 Message Set Migration Issue « View previous topic :: View next topic » 
Author Message
mqmaniac
PostPosted: Tue Jun 20, 2006 11:35 am    Post subject: WMQI 2.1.9 Message Set Migration Issue Reply with quote

Master

Joined: 27 Dec 2005
Posts: 201

Hello Everyone,

I am having he following Issue while migrating Message Sets from 2.1 to V5.0.

I see the following error for the Sets:

"Element "cc" must be rendered as an attribute when its enclosing group is nested more than one leveldeep in complex type "nnn";

I searched the IBM site and got following Information:

mqsimigratemsgsets command

. Defect 34872

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'." is caused by the way in which 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:

1. 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.

2. 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


My Question is :

1.Is there a Fix pack which can be applied to bypass the above workarounds?

2.Is these the ONLY ways to Handle ???


Pls Help
Back to top
View user's profile Send private message
kimbert
PostPosted: Wed Jun 21, 2006 5:09 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

Quote:
1.Is there a Fix pack which can be applied to bypass the above workarounds?
No
Quote:
2.Is these the ONLY ways to Handle ???
I don't know of any other way to correct the problem. Do you still have the original DTD/schema? If you do, option 1 is very straightforward.
Back to top
View user's profile Send private message
mqmaniac
PostPosted: Wed Jun 21, 2006 5:13 pm    Post subject: Reply with quote

Master

Joined: 27 Dec 2005
Posts: 201

This is strange...

I have applied fixpack 7 to MB v5.0 and Then I migrated the Message sets and It does not show me this error.

I think CSD 7 has the Fixes...
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » WMQI 2.1.9 Message Set Migration Issue
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.