|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Not able to create Message Definition Files from XSD |
« View previous topic :: View next topic » |
Author |
Message
|
satchin |
Posted: Fri Dec 09, 2011 6:47 pm Post subject: Not able to create Message Definition Files from XSD |
|
|
Apprentice
Joined: 08 Feb 2011 Posts: 33
|
Hi,
I am trying to create 2 message definition files (request and response messages) based on 2 different XSDs, but I am getting the below exception message in the toolkit after creating.
Description Resource Path Location Type
A Message Set can not contain two global element declarations with the same name and namespace (target or chameleon): '#empid' EmpIDRequest.mxsd CallMessageSet/CallMessageSet line 5 Cached Message Set Core Validation Problem
Description Resource Path Location Type
A Message Set can not contain two global element declarations with the same name and namespace (target or chameleon): '#empid' EmpIDResponse.mxsd CallMessageSet/CallMessageSet line 4 Cached Message Set Core Validation Problem
Please provide me the solution how to create these 2 message defintion files.
Many thanks in advance. |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Dec 09, 2011 7:33 pm Post subject: Re: Not able to create Message Definition Files from XSD |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
satchin wrote: |
Hi,
I am trying to create 2 message definition files (request and response messages) based on 2 different XSDs, but I am getting the below exception message in the toolkit after creating.
Description Resource Path Location Type
A Message Set can not contain two global element declarations with the same name and namespace (target or chameleon): '#empid' EmpIDRequest.mxsd CallMessageSet/CallMessageSet line 5 Cached Message Set Core Validation Problem
Description Resource Path Location Type
A Message Set can not contain two global element declarations with the same name and namespace (target or chameleon): '#empid' EmpIDResponse.mxsd CallMessageSet/CallMessageSet line 4 Cached Message Set Core Validation Problem
Please provide me the solution how to create these 2 message defintion files.
Many thanks in advance. |
This has nothing to do with the broker. Just think about XML best practices 1o1.
Your problem is in the setup of your xsd files. You should not have the same global definition (i.e. employee id) in 2 different xsd files.
You will need to create an xsd file containing that definition and that is referenced by both the request xsd and the reply xsd. By the way why aren't both request and reply in the same xsd ?  _________________ MQ & Broker admin |
|
Back to top |
|
 |
satchin |
Posted: Sat Dec 10, 2011 4:21 pm Post subject: |
|
|
Apprentice
Joined: 08 Feb 2011 Posts: 33
|
Thanks for your reply.
I am getting the same exception for 5 more tags, we cannot maintain these tags in one xsd because we need to expose this service to 2 different applications. Few tags are mandatory for one application and those tags are optional for the other application, thats why I am not able to put request and response in one xsd. |
|
Back to top |
|
 |
mqjeff |
Posted: Sat Dec 10, 2011 5:03 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
You can create a single XSD that defines the actual elements themselves.
You can then create one XSD that defines the request and response messages for the first application, and imports or includes the XSD that defines the elements.
You can then create a third XSD that defines the request and response messages for the second application, importing or including the XSD that defines the elements.
The issue you have cited is that you are trying to define the same global element twice in the same namespace. You can't do that. |
|
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
|
|
|
|