| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WBI MB-XML Namespace issue |
« View previous topic :: View next topic » |
| Author |
Message
|
| MQWizard |
 Posted: Thu Sep 14, 2006 12:24 pm Post subject: WBI MB-XML Namespace issue |
 |
|
Novice
Joined: 14 Sep 2006
Posts: 13
|
Hi,
Hi,
I need inputs from you guys to resolve this issue.
I am using XML which is Namespace aware and I am using MRM domain in my messageset for creating the structure.
Let me explain you my requirement - I have many xsd structure IN my object definitions belonging to different namespaces. these xsd structures represent objects (used by business). these objects refer to each other and are present in different namespaces.
Also, I have a common Parent envelope structure, which wraps the underlying objects. This envelope structure is a wrapper.
This wrapper need to be extended further by multiple xsds (message definitions) to construct their individual message.
Let me try to make things more clear- envelope is a common structure which will be able to wrap the underlying objects. Parent envelope needs to be extended, since different types of messages (request/reply, publish, different object propagations etc) may need to have a different underlying object/s under the request/response element of the parent envelope. so each type of messages will need to use its own child envelope extending the parent envelope xsd definition.
I have created parent envelope in one namespace, the first child envelope (or the first actual message structure) in other namespace and referred to the first one. It worked as expected. but when I create a second child envelope xsd under a different namespace and refer to the parent envelope, it gives me an error saying that duplicate elements are created.
I see this error only for the message element and not if the types/elements are duplicated across different message definitions. It looks like even if it belongs to different namespace, mb does not allow to have same name of messages within a single messageset/messageset project.
Pls let me know, if I have done something wrong. If not, what will be the best way to acheive, what I want to do.
thanks.
_________________
Wizard Leads the way |
|
| Back to top |
|
 |
| JosephGramig |
| Posted: Fri Sep 15, 2006 10:04 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Did you build a Message Set Project and import all your XSD files and validate them?
Are you going to do SOAP with these?
_________________
Joseph
Administrator - IBM WebSphere MQ (WMQ) V6.0, IBM WebSphere Message Broker (WMB) V6.1 & V6.0
Solution Designer - WMQ V6.0
Solution Developer - WMB V6.1 & V6.0, WMQ V5.3 |
|
| Back to top |
|
|
| MQWizard |
| Posted: Fri Sep 15, 2006 11:23 am Post subject: |
|
|
Novice
Joined: 14 Sep 2006
Posts: 13
|
The issue which I have mentioned is what I am experiencing in message set and while creating message definition for the second child envelope message (.mxsd file).
I am using MRM and and as mentioned facing an issue when I am importing the second child envelope message (.xsd file).
The issue is, it has the same message name and MB is throwing an error.
As far as XML standard is concerned, if it belongs to a different namespace it should work fine but it looks like MB is not following this specification, when the element is selected as a message in the message definition file.
I am looking forward to you guys to provide some other good way to acheive this, if the namespace is not fully supported by MB at the message level.
_________________
Wizard Leads the way |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Sep 15, 2006 12:21 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
The restriction which you have encountered is a known limitation of message sets. You cannot have two messages with the same name, even if they are in different namespaces. We know that this is non-ideal, and we are keen to fix it if/when we get the chance. That last sentence means exactly what it says, by the way - it is not an announcement about the content of any future release of message broker.
I would need a better understanding of your requirements before I suggested a workaround. In fact, you seem to have a good knowledge of XML schema, so you are probably in the best position to find the solution. |
|
| Back to top |
|
|
| MQWizard |
| Posted: Mon Sep 18, 2006 11:13 am Post subject: |
|
|
Novice
Joined: 14 Sep 2006
Posts: 13
|
Hi,
thanks for the reply and thanks for the confirmation on the product support.
My understanding is the only solution, I have is to create many message sets (as many child envelope structure I have) and in each message set have all the xsds in it- all of the object xsds it require, common xsds and the common parent envelope xsds
thank all of you for your prompt inputs.
_________________
Wizard Leads the way |
|
| 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
|
|
|
|
