| Author |
Message
|
| mahesh2069 |
 Posted: Wed Jul 10, 2013 4:55 am Post subject: Problem in build SOAP Response in JCN with name space |
 |
|
Centurion
Joined: 26 Jun 2013
Posts: 103
|
Hi ALL,
I have a simple flow,
SOAP input --> JCN ---> SOAP Reply
I have given input through SOAP UI, Input message contain some soap input with name space ,In JCN I just modify the input soap body and create structure of output message,but error is coming in while send response from soap reply to soap ui, After JCN that structure go to SOAP reply..Here error is coming after go to infinite loop..
I want to generate namespace based response..But problem in create name space for output structure ,where do we add name space??
error is " <com.ibm.broker.plugin.MbBrokerException source:BIPmsgs key:3752 message:[BIPmsgs:3752]BIP3752E: The SOAP Reply node 'Error occurred in ImbSOAPReplyHelper::makeSOAPReply()' encountered an error while processing a reply message.
An error occurred during reply message processing. "
Error occurred in ImbSOAPReplyHelper::makeSOAPReply() >
_________________
Thanks & Regards
Mahesh Mediboyina
WMB Developer |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Wed Jul 10, 2013 5:09 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| mahesh2069 |
| Posted: Wed Jul 10, 2013 6:04 am Post subject: |
|
|
Centurion
Joined: 26 Jun 2013
Posts: 103
|
Already I had done in Compute node ,But I need to do same in JCN , problem when we generate name space based outputs in java compute node.
Give me some Idea's to do..
_________________
Thanks & Regards
Mahesh Mediboyina
WMB Developer |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Jul 10, 2013 6:32 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Jul 10, 2013 6:55 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| mahesh2069 wrote: |
| Already I had done in Compute node ,But I need to do same in JCN , problem when we generate name space based outputs in java compute node. Give me some Idea's to do.. |
If you already had it working in an ESQL Compute node, why do you need to change to JCN?
The whole benefit of ESQL is the ease of working with the Logical Message Tree including namespaces. ESQL is a purpose-built language for WebSphere Message Broker that has specific linguistic constructs to manipulate the Logical Message Tree including namespaces.
Java is a general purpose langauge which lacks the sophistication of the ESQL language when it comes to efficiently addressing the Logical Message Tree including namespaces.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mahesh2069 |
| Posted: Wed Jul 10, 2013 8:20 am Post subject: |
|
|
Centurion
Joined: 26 Jun 2013
Posts: 103
|
Yah.. your are correct ESQL is correct way to do, but my client said that "use JCN to do "
Help me to solve..that issue.
_________________
Thanks & Regards
Mahesh Mediboyina
WMB Developer |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Jul 10, 2013 8:29 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Your code is building the wrong message.
You haven't shown the message your code is building.
You haven't shown your code.
So you need to troubleshoot your code until it produces the correct message. It helps to know before hand what the correct message is supposed to look like. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Jul 10, 2013 9:23 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Jul 10, 2013 11:28 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| lancelotlinc wrote: |
]
]Your manager with no message flows in production is telling that you are not allowed to use <xyz> node.[/url] |
But the Customer is always right (sic)
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Jul 10, 2013 6:39 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
And there are probably more Java resources in the company than ESQL resources. The question is have these Java resources been trained on WMB. If not there is a huge risk exposure...(its like putting a tractor driver behind the wheel of a Ferrari) 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Jul 11, 2013 3:37 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Jul 11, 2013 3:40 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| fjb_saper wrote: |
| And there are probably more Java resources in the company than ESQL resources. The question is have these Java resources been trained on WMB. If not there is a huge risk exposure...(its like putting a tractor driver behind the wheel of a Ferrari) |
Someone who has Java experience that cannot write ESQL code ought to have their head examined. ESQL is a fine language and far less difficult than Java. ESQL is very well documented. The language is not the problem.
A poorly written WMB message flow would be poorly written in either Java or ESQL. Thats because the poorness (is that even a word?) comes from lack of understanding about how Broker works rather than the language the code is implemented in.
In other words, the risk is from a lack of understanding how to manipulate the Logical Message Tree rather than if the code is written in Java or ESQL. The risk is huge, but not because of the language.
Even if there are more Java people in the company, not one of them would be any good at WMB without understanding CreateNextSibling which is implemented in ESQL and Java the same way.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
|
|
