Author |
Message
|
sandman147 |
Posted: Tue Jan 14, 2014 7:25 am Post subject: Writing SOAP message to Queue Issue |
|
|
Apprentice
Joined: 01 Sep 2013 Posts: 42
|
I have with me a flow that writes the SOAP request message to a queue after extracting the SOAP envelope.
The Issue:
In SOAP UI
<soapenv:Envelope >
<soapenv:Header/>
<soapenv:Body>
<tes:TestOperation>
<Request>name: tom hardy
zip = 900087
phone; 546-987-9909
</Request>
</tes:TestOperation>
</soapenv:Body>
</soapenv:Envelope>
Output in Queue
<Request>name: tom hardy.zip = 900087.phone; 546-987-9909. </Request>
The line feed (a new line) from SOAP UI is represented as a '.' in the Queue.
The Request element from my msg set is of type string. What changes should I do so that I may receive in my output queue the exact string (strings separated by line feed) as printed in the soap UI |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Jan 14, 2014 7:33 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
The line feed is represented as a sequence of bytes on the queue. It's not represented as a ".".
This sequence of bytes may happen to be displayed as "." in whatever you are using to display the bytes of the message on the queue.
But that doesn't mean that it's the wrong sequence of bytes. |
|
Back to top |
|
 |
smdavies99 |
Posted: Tue Jan 14, 2014 7:40 am Post subject: |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
I second what 'mqjeff' has said.
Browse the message with a tool such as 'rfhutil' or amqsbcg. Both of these can show the HEX value that your flow has written,
Just using MQExplorer won't show you the real values. _________________ 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 |
|
 |
sandman147 |
Posted: Tue Jan 14, 2014 8:42 am Post subject: |
|
|
Apprentice
Joined: 01 Sep 2013 Posts: 42
|
Thank you for your valuable inputs |
|
Back to top |
|
 |
|