| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| unknown elements created in tree after SOAPEnvelope node |
« View previous topic :: View next topic » |
| Author |
Message
|
| chocobo0079 |
 Posted: Tue Jun 03, 2008 11:40 pm Post subject: unknown elements created in tree after SOAPEnvelope node |
 |
|
Newbie
Joined: 29 May 2008
Posts: 4
|
Hi,
I have a message flow auto. generated from wsdl by dang and drop the wsdl file to message flow file, like this:
HTTPInput -> (SOAPExtract)(generated subflow) -> Compute -> SOAPEnvelope -> HTTPreply
And two XML schema for request and reply like this:
<mxsd:complexType name="RequestInput1">
<mxsd:sequence>
<mxsd:element minOccurs="0" name="A" type="mxsd:string"/>
<mxsd:element minOccurs="0" name="B" type="mxsd:date"/>
</mxsd:sequence>
</mxsd:complexType>
<mxsd:element name="RequestInput1" type="RequestInput1">
</mxsd:element>
And,
<mxsd:complexType name="ReplyOutput1">
<mxsd:sequence>
<mxsd:element minOccurs="0" name="C" type="mxsd:string"/>
</mxsd:sequence>
</mxsd:complexType>
<mxsd:element name="ReplyOutput1" type="ReplyOutput1">
</mxsd:element>
The output MRM message tree is fine before pass through SOAPEnvelope, like this:
MRM
+-ReplyOutput1
+-C
+-C
+-C.....
But after the SOAPEnvelope, the tree become like this:
MRM
+-NULL Body
+-NULL ReplyOutput1
+-ReplyOutput1
+-C
+-C
+-C.....
If I add the throw node at SOAPEnvelope Failure,
the exception is: "move to next sibling failed."
I think the failed next sibling movement is due to the wrong message tree and the output XML schema.
Can any one tell me why the tree become like this? Thanks. |
|
| Back to top |
|
 |
| kimbert |
| Posted: Wed Jun 04, 2008 12:48 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
You should disconnect the debugger when you get a parsing error - the tree which it displays will not always be accurate. My usual advice is to add Trace nodes to the message flow and take a user trace. That way, you get a clear picture of what is happening.
Please state which version and fix pack you're on. |
|
| Back to top |
|
|
| chocobo0079 |
| Posted: Wed Jun 04, 2008 2:23 am Post subject: |
|
|
Newbie
Joined: 29 May 2008
Posts: 4
|
Thanks, kimbert,
It is WebSphere Message Brokers Toolkit - Message Broker, Version: 6.0.2,
Build id: 20061201_1308 |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Jun 04, 2008 1:28 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
I don't understand your notation for describing message trees. Please post the Trace node output(s) (and please use [code] tags to preserve the indentation )
One method is to add Trace nodes and take a User Trace, as I advised before:
| Quote: |
| add Trace nodes to the message flow and take a user trace |
|
|
| 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
|
|
|
|
