| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| XML wire Format |
« View previous topic :: View next topic » |
| Author |
Message
|
| tonythomasantony |
 Posted: Wed Sep 26, 2007 3:16 am Post subject: XML wire Format |
 |
|
Apprentice
Joined: 12 Aug 2006
Posts: 47
|
Hi ,
i defined one message in a message set (XML wire format).
Message (Details)contains 2 elements Name and ID.Minimum and Maximum occurance is 1
I selected this message set,type,format in MQInput node.And put message in this format
<Details><Name>Tony</Name><ID1>33</ID1></Details>
I expect this will throw an error bcz of the absence of ID and also the presence of ID1.
But nothing happened and also it successfully put in the Out Put Queue.
I just cant understand the message parsing using message definitions.
This is very basic question  ..But please give some light on ,
What is the real use of Message sets for XML wire format in MRM domain..
regards,
Tony Thomas |
|
| Back to top |
|
 |
| kimbert |
| Posted: Wed Sep 26, 2007 4:01 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
You need to enable validation in your message flow.
Go to the input node properties, and set 'Validation' to 'Content and Value'.
| Quote: |
| What is the real use of Message sets for XML wire format in MRM domain |
If you don't deploy the message set, how can the MRM XML parser act on the information contained in it? |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Sep 26, 2007 4:05 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You also need to ensure that the message is associated with your message set.
This is usually done by setting the default Message Parsing properties on the Input node.
Although it's a bit trickier with XML.
ALSO, you need to make sure your message is of Type Composition "Closed", if you want it to throw an error for <ID1>.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| tonythomasantony |
| Posted: Wed Oct 03, 2007 5:26 am Post subject: |
|
|
Apprentice
Joined: 12 Aug 2006
Posts: 47
|
actually my message definition in which the message resides references to other message definition and all types having composition set to closed,including the referenced and Input node also enabled with validation content and value.But validation is failing for incorrect messages and the message receives in the out put node without any problem
i have created one more message definition without any reference to other definitions.The message in this message sets parses properly for bad messages...
what will be the solution for the messages which is having imports?
regards,
Tony Thomas |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Oct 04, 2007 11:56 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
I suspect that your entire message is 'self-defining' ( not matched against a message definition in your message set ).
Which version of WMB are you using? If it is not v6, check that 'Root tag name' in the XML message set properties is empty ( it defaults to 'MRM' in v5 ).
Check that the name and namespace of your tags match the names and namespaces in the message definition If necessary, put a trace node into your flow so that you can see the message tree which is being validated. |
|
| 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
|
|
|
|
