| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| XML Parsing Errors restoring SOAP Envelope |
« View previous topic :: View next topic » |
| Author |
Message
|
| servi |
 Posted: Mon Jun 21, 2010 6:35 am Post subject: XML Parsing Errors restoring SOAP Envelope |
 |
|
Novice
Joined: 19 Mar 2008
Posts: 22
Location: Madrid, España
|
Hi,
I have done a message Flow to provide a SOAP Web Service. Initaly the ExtractEnvelopeNode and the SoapReply was in the same flow and everythings goes well.
For asyncronus propouses, I need to separate it in two flows:
SOAPInput-->ExtractEnvelope-->Compute1-->MQOutput(calls a MQService in Msg1)
MQInput(response)-->Compute2-->SOAPReply
I have save the SOAP ReplyIdentifier in the XML(XMLNSC) Msg1:
SET OutputLocalEnvironment.Destination.SOAP.Reply.ReplyIdentifier = CAST( OutputLocalEnvironment.Destination.SOAP.Reply.ReplyIdentifier AS BLOB);
But I can save the SOAP.Envelope properly. I save it in the OutputRoot, but when is readed by MQInput XML parsing errors occurs.
I have also tried to convert the SOAP.Envelope to BLOB and restore it in Compute2, but the same XML parsing errors occurs.
Compute 1:
....
DECLARE EnvelopeAsBitStream BLOB ASBITSTREAM(InputLocalEnvironment.SOAP.Envelope CCSID 1208);
SET OutputLocalEnvironment.Variables.Mapfre.INFO.SOAP.Envelope = EnvelopeAsBitStream;
...
Compute2:
....
CREATE FIRSTCHILD OF OutputLocalEnvironment.SOAP DOMAIN 'XMLNSC' PARSE( InputRoot.XMLNSC.MIDDLEWARE.INFO.SOAP.Envelope, InputProperties.Encoding, InputProperties.CodedCharSetId,'','','',FolderBitStream);
...
¿Has anyone store the SOAP Envelope in a XMLNSC message?
Thanks in advance, |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Jun 21, 2010 7:33 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You may have to save it as 64 bit encoded BLOB.
We do this with the MQMD node information on aggregation and add a specific message to the aggregation for carrying the MQMD stuff.
You may have to resort to the same kind of trick.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mgk |
| Posted: Mon Jun 21, 2010 8:47 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Do you really need to save the envelope at all? The SOAPReply node will create a default one for you automatically if one is not present...
Kind Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jun 21, 2010 9:26 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| mgk wrote: |
Do you really need to save the envelope at all? The SOAPReply node will create a default one for you automatically if one is not present...
Kind Regards, |
If I understood him well, it is not about saving the envelope, it is about saving connection information, like replyto and session information/identifiers
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Jun 21, 2010 10:49 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
But I can save the SOAP.Envelope properly. I save it in the OutputRoot, but when is readed by MQInput XML parsing errors occurs.
I have also tried to convert the SOAP.Envelope to BLOB and restore it in Compute2, but the same XML parsing errors occurs. |
There are dozens of different XML parsing errors. It's quite hard to diagnose your problem without knowing what error you are getting. Please quote the XML parser error ( all of it ). If necessary, take a user trace to make sure that you get the entire error message. |
|
| 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
|
|
|
|
