| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| parsing error for XMLNCS header |
« View previous topic :: View next topic » |
| Author |
Message
|
| fde |
 Posted: Wed Aug 06, 2008 4:42 am Post subject: parsing error for XMLNCS header |
 |
|
Acolyte
Joined: 05 Jul 2007
Posts: 65
|
Hi folks,
webservice-flow:
Soap-input with generated Soap extraxt sublow, mapping(webservice mset to mq mset), MQ-Output, MQ-Get, mapping(mq mset to ws mset), Soap-Reply
mq-flow:
MQ-Input, Mapping, MQ-Output
webservice mset:
Domain Soap(Default), XMLNSC
XML wireformat
mq-mset:
Domain XMLNSC(Default)
XML wireformat
problem:
MQ-Output writes the message to a queue. The message cannot be parsed after reading it again from the queue. Even by trying to parse to XMLNSC domain without any Messageset specified.
RFHUtil shows the following for the message:
| Code: |
HTTP/1.1 200 OK..Content-Type: text/xml;charset=utf-8..Content-Length: 275..Date: Wed, 06 Aug 2008 12:21:47 GMT..Server: Apache-Coyote/1.1....
<NS1:myRequest xmlns:NS1="http://www.mynamespace.com">
<<validXML>>
</NS1:myRequest>
|
I wonder about the unformated header and the non existent xml-Deklaration. "Suppress xml-Deklaration" is not set for XML-wireformat.
Do you have any advice for me?
Did I miss something regarding the message domains?
_________________
Global warming is an unintentional side effect of SOA's hotness.
-- http://soafacts.com/
a business integration methodology |
|
| Back to top |
|
 |
| sridhsri |
| Posted: Wed Aug 06, 2008 5:07 am Post subject: |
|
|
Master
Joined: 19 Jun 2008
Posts: 297
|
| The "HTTP/1.1....." is not XML declaration. That is a part of the HTTP Header. Perhaps when you are writing the message to the queue, you are also writing these headers. Don't copy the message headers when you write the message to the queue. |
|
| Back to top |
|
|
| fde |
| Posted: Wed Aug 06, 2008 5:22 am Post subject: |
|
|
Acolyte
Joined: 05 Jul 2007
Posts: 65
|
| sridhsri wrote: |
| Don't copy the message headers when you write the message to the queue. |
Ah, very good. In debug i just saw the HTTP-ResponseHeader containing just the information from the top of the message.
Now, since I use the mapping-node and no esql, I wasnt aware that I copied the Header too. The mapping script just contains a call to a supmap, which maps the Body of the Message.
I will investigate in this.
Thank you.
EDIT:
HTTP-Header-Node from Transportheadernodes does the trick for me with a property "Delete HTTP-ResponseHeader".
_________________
Global warming is an unintentional side effect of SOA's hotness.
-- http://soafacts.com/
a business integration methodology
Last edited by fde on Wed Aug 06, 2008 5:37 am; edited 1 time in total |
|
| Back to top |
|
|
| kimbert |
| Posted: Wed Aug 06, 2008 5:28 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| "Suppress xml-Deklaration" is not set for XML-wireformat. |
But it it *was* set, would it suppress the XML declaration? No, because XMLNSC does not actually use any of the information in messageSet.mset. It only uses the mxsds.
You are not the first to make that mistake, and the docs should really be clearer about this. |
|
| Back to top |
|
|
| fde |
| Posted: Wed Aug 06, 2008 5:40 am Post subject: |
|
|
Acolyte
Joined: 05 Jul 2007
Posts: 65
|
| Quote: |
| XMLNSC does not actually use any of the information in messageSet.mset. It only uses the mxsds. |
Very interesting. Thanks for pointing out, I have to check my message set and the infocenter again now.
Anyway, after deleting the Http-Header, the message is parsed fine.
_________________
Global warming is an unintentional side effect of SOA's hotness.
-- http://soafacts.com/
a business integration methodology |
|
| 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
|
|
|
|
