MQSeries.net :: View topic - Is it possible to parse SOAP message using Create Statement

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Is it possible to parse SOAP message using Create Statement

Is it possible to parse SOAP message using Create Statement

« View previous topic :: View next topic »

Author

Message

sandy vish

Posted: Wed Feb 27, 2013 5:08 am Post subject: Is it possible to parse SOAP message using Create Statement

Apprentice

Joined: 18 Nov 2012
Posts: 27

Is it possible to parse SOAP message using Create Statement

Quote:

CREATE LASTCHILD OF creationPtr DOMAIN('SOAP') PARSE(InputRoot.BLOB.BLOB,
InputProperties.Encoding,
InputProperties.CodedCharSetId);

...if So please let us know

lancelotlinc

Posted: Wed Feb 27, 2013 5:18 am Post subject:

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

When you execute the above statement, what happens?

Why ask here when you can try it on your own?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER

sandy vish

Posted: Wed Feb 27, 2013 5:28 am Post subject:

Apprentice

Joined: 18 Nov 2012
Posts: 27

Thnk u for the quick response, i have tried the same and got the below error "problem creating SOAP tree from bitstream", so my point of asking is "IS IT POSSIBLE to do or not" Please enlighten us....

mqjeff

Posted: Wed Feb 27, 2013 5:41 am Post subject:

Grand Master

Joined: 25 Jun 2008
Posts: 17447

IF we tell you it *is* possible, what steps will you then take after that?

IF we tell you it is *not* possible, what steps will you take after that?

What steps will you take to determine if we have given you the *correct* answer?

"Problem creating SOAP tree from bitstream" doesn't mean "you aren't allowed to create a SOAP tree from a bitstream".

It means "It didn't work to create a SOAP message from *this* bitstream".

Note that this does not answer the question you have directly asked, and so I am clearly being unhelpful.

sandy vish

Posted: Wed Feb 27, 2013 5:49 am Post subject:

Apprentice

Joined: 18 Nov 2012
Posts: 27

Thnku jeff, So is it advisable to parse in this manner?there is a plan "A" using soap Extract and then parse, which is working now...so

Quote:

IF we tell you it *is* possible, what steps will you then take after that?

then ill try to parse with the correct syntax provided by you..

thank u once again

mqjeff

Posted: Wed Feb 27, 2013 6:00 am Post subject:

Grand Master

Joined: 25 Jun 2008
Posts: 17447

sandy vish wrote:

Thnku jeff, So is it advisable to parse in this manner?

That depends.

sandy vish wrote:

there is a plan "A" using soap Extract and then parse, which is working now...so

So why are you looking at alternatives?

sandy vish wrote:

Quote:

IF we tell you it *is* possible, what steps will you then take after that?

then ill try to parse with the correct syntax provided by you..

I didn't say we would provide correct syntax. I merely said we would confirm that it was possible.

And I'll even do that much. I'll confirm that it is possible to parse a proper bitstream into a SOAP message tree.

lancelotlinc

Posted: Wed Feb 27, 2013 6:24 am Post subject:

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

sandy vish wrote:

Thnku jeff, So is it advisable to parse in this manner?there is a plan "A" using soap Extract and then parse, which is working now...so

Quote:

IF we tell you it *is* possible, what steps will you then take after that?

then ill try to parse with the correct syntax provided by you..

thank u once again

Are you offering compensation for consulting services? I have some spare time, I could come on your site.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER

sandy vish

Posted: Wed Feb 27, 2013 6:26 am Post subject:

Apprentice

Joined: 18 Nov 2012
Posts: 27

yes plz ...Please share your account details....lol....

Vitor

Posted: Wed Feb 27, 2013 6:28 am Post subject:

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

sandy vish wrote:

So is it advisable to parse in this manner?

It's potentially more efficient, as there are fewer steps.

sandy vish wrote:

there is a plan "A" using soap Extract and then parse, which is working now...

So what does that tell you about why your previous attempt failed?

sandy vish wrote:

mqjeff wrote:

IF we tell you it *is* possible, what steps will you then take after that?

then ill try to parse with the correct syntax provided by you..

How do you know the syntax is the problem? Given how you've "resolved" the problem?
_________________
Honesty is the best policy.
Insanity is the best defence.

lancelotlinc

Posted: Wed Feb 27, 2013 6:33 am Post subject:

Jedi Knight

Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA

sandy vish wrote:

yes plz ...Please share your account details....lol....

My email link is available in my profile and on my posts. Please forward your offer.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER

sandy vish

Posted: Thu Feb 28, 2013 6:01 am Post subject:

Apprentice

Joined: 18 Nov 2012
Posts: 27

user trace gives me

Quote:

2013-02-28 19:15:52.767948 4616 RecoverableException BIP2230E: Error detected whilst processing a message in node 'ParseSoapMsg.Trace'.
The message broker detected an error whilst processing a message in node 'ParseSoapMsg.Trace'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2013-02-28 19:15:52.767963 4616 ParserException BIP3614E: A SOAP logical tree cannot be built from the message bitstream.
The bitstream is not a valid Web service message.
Review further error messages for an indication to the cause of the error.
2013-02-28 19:15:52.767982 4616 ParserException BIP3606E: The bitstream is not an XML serialization of a SOAP logical tree.
When the SOAP parser is not invoked from a SOAP node, it expects the bitstream to be the serialized XML representation of the SOAP domain tree as generated by the asbitstream function. This representation of the SOAP tree is provided for internal broker use in aggregation scenarios.
Check the bitstream being parsed and either ensure it is a valid XML representation of the SOAP domain tree, or parse it in a different domain.

Inputs plz

fjb_saper

Posted: Thu Feb 28, 2013 6:13 am Post subject:

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

sandy vish wrote:

user trace gives me

Quote:

Inputs plz

If your service is a restful service you can only parse in the XMLNSc/XMLNS domains.
The error message is telling you that you're not in the presence of a SOAP bitstream.

How did you create the message?

Have fun

_________________
MQ & Broker admin

mgk

Posted: Thu Feb 28, 2013 7:08 am Post subject:

Padawan

Joined: 31 Jul 2003
Posts: 1642

Essentially, the answer is no - simply switch to using the XMLNSC parser instead in this case. The SOAP parser expects that the tree is a "soap_domain_msg" when it is used in this scenario - it is looking for a bistream that was created with an ASBitstream of a SOAP parser and this is not the same as a regular SOAP message.

Kind regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Is it possible to parse SOAP message using Create Statement

Jump to:

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

Protected by Anti-Spam ACP