|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
HTTP Error Status Code 500, but SOAP Fault missing |
« View previous topic :: View next topic » |
Author |
Message
|
wmqstankela |
Posted: Thu Nov 17, 2016 7:09 am Post subject: |
|
|
Voyager
Joined: 29 Feb 2016 Posts: 94
|
You are totally right mqjeff. I used this code and everything works fine:
Code: |
DECLARE inCCSID INT InputProperties.CodedCharSetId;
DECLARE inEncoding INT InputProperties.Encoding;
CREATE LASTCHILD OF OutputRoot DOMAIN('XMLNSC') PARSE(InputRoot.XMLNSC.error.BLOB, inEncoding, inCCSID); |
Thanks a lot guys! |
|
Back to top |
|
|
mqjeff |
Posted: Thu Nov 17, 2016 7:37 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
wmqstankela wrote: |
You are totally right mqjeff. I used this code and everything works fine:
Code: |
DECLARE inCCSID INT InputProperties.CodedCharSetId;
DECLARE inEncoding INT InputProperties.Encoding;
CREATE LASTCHILD OF OutputRoot DOMAIN('XMLNSC') PARSE(InputRoot.XMLNSC.error.BLOB, inEncoding, inCCSID); |
Thanks a lot guys! |
From the message data you showed
wmqstankela wrote: |
<xsd:Response>
<xsd:CommonResponse>
<xsd:error>
<xsd:errorCode>Error-E001</xsd:errorCode>
</xsd:error>
</xsd:CommonResponse>
</xsd:Response> |
I still don't see any BLOB... you should simply be able to do something like
Code: |
SET OutputRoot.XMLNSC = InputRoot.XMLNSC.*:Response.*:CommonResponse.*.error |
_________________ chmod -R ugo-wx / |
|
Back to top |
|
|
wmqstankela |
Posted: Fri Nov 18, 2016 1:00 am Post subject: |
|
|
Voyager
Joined: 29 Feb 2016 Posts: 94
|
That response is in hex format. I don't see this XML from http request node. I see message in hex format. Http request propagate it to error terminal and parse it like BLOB and thats why I need to convert it to XML tree. |
|
Back to top |
|
|
mgk |
Posted: Fri Nov 18, 2016 1:16 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003 Posts: 1638
|
Quote: |
Http request propagate it to error terminal and parse it like BLOB and thats why I need to convert it to XML tree. |
Have your tried using the SOAP Node and wiring up the "Fault" terminal? If it is a valid SOAP Fault message, then it should be sent to the Fault terminal as a SOAP message, so you don't need to do anything... _________________ 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 |
|
|
wmqstankela |
Posted: Fri Nov 18, 2016 2:01 am Post subject: |
|
|
Voyager
Joined: 29 Feb 2016 Posts: 94
|
It's not soap fault message...read the post from the top. I used soap request but node throws exception because http response code was 500 and no soap fault element found.
I've resolved problem by using http request node and convert hex response from error terminal to XML tree.
You all help me a lot. Thank you guys! |
|
Back to top |
|
|
|
|
|
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
|
|
|
|