|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Not able to read input message, used XMLNSC parser |
« View previous topic :: View next topic » |
Author |
Message
|
satchin |
Posted: Mon Mar 19, 2012 8:00 am Post subject: Not able to read input message, used XMLNSC parser |
|
|
Apprentice
Joined: 08 Feb 2011 Posts: 33
|
Hi All,
I developed message flow MQInput->Compute->MQOutput.
Not able read input message and assign to output message, I have created the message defintion files based on XSD and used XMLNSC parser.
I am trying to get account no from input message and assign it to output message, below is my ESQL code.
SET OutputRoot.XMLNSC.ns:AcctRequest.ns:Accounts.ns:AcctountNum=InputRoot.XMLNSC.ns1:CUstRequest.ns1:Accounts.ns1:AcctountNum;
In the output queue message inserted without any values, <AcctRequest><Accounts/></AcctRequest>
Please help me how to access input message and assign it to output message in this scenario.
Many thanks in advance. |
|
Back to top |
|
 |
lancelotlinc |
Posted: Mon Mar 19, 2012 8:08 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
When you put a trace node after your Compute node, what do you see in the trace output? When you use the interactive debugger, what namespace do you see on the InputRoot? When you turn on User Trace, what data do you see in the User Trace output? _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
Vitor |
Posted: Mon Mar 19, 2012 8:14 am Post subject: Re: Not able to read input message, used XMLNSC parser |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
satchin wrote: |
SET OutputRoot.XMLNSC.ns:AcctRequest.ns:Accounts.ns:AcctountNum=InputRoot.XMLNSC.ns1:CUstRequest.ns1:Accounts.ns1:AcctountNum; |
That's an interesting capitalization of a tag name....
How do you know ns1 is the correct namespace?
How do you know that tag exists in the input?
What reason does the user trace give for not setting the output? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mattfarney |
Posted: Mon Mar 19, 2012 2:31 pm Post subject: |
|
|
 Disciple
Joined: 17 Jan 2006 Posts: 167 Location: Ohio
|
Just a suggestion:
Did you define and populate the namespace variables?
Code: |
DECLARE ns01 NAMESPACE 'http://www.openapplications.org/oagis'; |
Or whatever your namespaces actually represent.
Otherwise, I believe it thinks your namespaces are null.
-mf |
|
Back to top |
|
 |
kimbert |
Posted: Tue Mar 20, 2012 3:10 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
Your ESQL code is incorrect. Take a user trace to find out what is wrong.
If necessary, do some reading in the info center to learn about how to handle namespaces in ESQL. |
|
Back to top |
|
 |
satchin |
Posted: Tue Mar 20, 2012 2:06 pm Post subject: |
|
|
Apprentice
Joined: 08 Feb 2011 Posts: 33
|
Thanks all for your reply.
I solved the problem, it is related with namespace in input XML. |
|
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
|
|
|
|