| Author |
Message
|
| kimbert |
 Posted: Wed Aug 01, 2007 1:56 pm Post subject: |
 |
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
| Quote: |
| So once again - is it possible to say explicitly (in SET or somwhere) what the namespace should be used by broker? |
Of course. You either provide the full namespace URI on the SET statement, or you define a namespace constant and use that.
When you are copying from InputRoot to OutputRoot I would expect the namespace to be copied automatically. However, you are already in a situation where unexpected things are happening. So please do the following:
- Add a Trace node after the input node
- Add a Trace node before the output node
- Set the 'Destination' property on both Trace nodes to 'User Trace'
- Set Pattern to ${Root} on both Trace nodes
- Post the resulting user trace
- Post the contents of the relevant mxsd file ( unless it is absolutely huge ) |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Wed Aug 01, 2007 2:03 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Hrm.
MRM takes Namespace qualifiers?
Okay.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Aug 01, 2007 2:52 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
| jefflowrey wrote: |
Hrm.
MRM takes Namespace qualifiers?
Okay.
|
V6 it does, possibly even V5 but Kimbert would know that way better than me...
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kimbert |
| Posted: Thu Aug 02, 2007 1:33 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
| Quote: |
| MRM takes Namespace qualifiers? |
Namespaces are used in at least 3 ways in WMB.
a) in the message tree, as the NAMESPACE property of any syntax element
b) in the message tree, as a special 'namespace declaration' syntax element ( XMLNS and XMLNSC only )
c) in the message model
I'm referring to a). pawel_janowski can explicitly set the namespace of OutputRoot.MRM.Header.processingTimestamp if he wants to. |
|
| Back to top |
|
|
| pawel_janowski |
| Posted: Thu Aug 02, 2007 5:19 am Post subject: |
|
|
Apprentice
Joined: 13 Dec 2006
Posts: 38
|
Hi!
Finally I've managed to trap the problem. It was quite simple (to fix, not to find) - all complex datatypes were defined as sequences and the message tree was build in improper order (I had all elements in the tree but in incorrect order). That's why broker could not recognize the message.
Thanks to jefflowrey and kimbert for responses.
Regards.
Pawel
_________________
Pawel Janowski |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Aug 02, 2007 9:15 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
| pawel_janowski wrote: |
Hi!
Finally I've managed to trap the problem. It was quite simple (to fix, not to find) - all complex datatypes were defined as sequences and the message tree was build in improper order (I had all elements in the tree but in incorrect order). That's why broker could not recognize the message.
Thanks to jefflowrey and kimbert for responses.
Regards.
Pawel |
I have found that a validation node and a trace node on the catch of the validation will help no ends. The Exception Tree will hold some information (at least down to the last recognized node) and even tell sometimes what node is missing/expected, while $Root will show how the message tree is built....
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
