Posted: Thu Jul 29, 2010 11:45 am Post subject: indifferent behavior of XMLNSC parser in Windows and on AIX
Newbie
Joined: 29 Jul 2010 Posts: 6
I deployed a flow with a HTTPInput node using an XMLNSC parser.
I deployed this on a local windows-xp with WMB 6.1 as well as on an AIX box with WMB 6.1.
When I send a SOAP message with an invalid XML character (Unicode: 0xffffffff) to this flow,
I see different behavior with the flow deployed on windows from the one deployed on AIX.
on windows, the HTTPInput node could create the XMLNSC domain and parse the message until it found this invalid character
whereas on AIX, it doesn't parse the message at all as I don't see the XMLNSC domain in the message tree.
Posted: Thu Jul 29, 2010 11:55 am Post subject: Re: indifferent behavior of XMLNSC parser in Windows and on
Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
kandarpar wrote:
appreciate any ideas or thoughts on this
What level of v6.1 was used to generate the bar file?
What level of v6.1 is the broker on Windows?
What level of v6.1 is the broker on AIX?
When you say "see the domain in the message tree" I assume you're talking about the interactive debugger. This tool changes the parsing behaviour of broker by the simple fact of it's use. Is a user trace the same on both platforms?
Also why exactly are you surprised you can't see a parsed XML document in broker when there's an unparsable character in it? _________________ Honesty is the best policy.
Insanity is the best defence.
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