ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Problems with UTF-8 BOM parsing XML in WBIMB 5.0

Post new topic  Reply to topic
 Problems with UTF-8 BOM parsing XML in WBIMB 5.0 « View previous topic :: View next topic » 
Author Message
martinrydman
PostPosted: Fri Jan 30, 2004 7:17 am    Post subject: Problems with UTF-8 BOM parsing XML in WBIMB 5.0 Reply with quote

Centurion

Joined: 30 Jan 2004
Posts: 139
Location: Gothenburg, Sweden

Hi all!

I've got a XML message containing x'ef bb bf' as a BOM. This message can be opened with a variety of XML-parser. (I've tried IE and XML-spy). I lift this message with RFHUTIL and put it to a queue feeding a messageflow that lifts the message via an Input node configured with the XML domain. When I try to trace it, I get an error, 5004 (An error has been reported by the BIPXML4C component). RFHUTIL will produce MQMD.CodedCharSetId = 437 (not utf-. Changing it (in RFHUTIL) to 1208 (utf- does not help (the trace confirms that CCSID has been changed to 1208).

Now, if I use an hex-editor to delete the BOM, the message is parsed and traced as expected.

I try to pinpoint if this is an error in the message, a bug in the parser, some inconsitency between headers and pay-load, etc.

Any help/hints greatly appreciated.

TIA

/Martin
Back to top
View user's profile Send private message
wooda
PostPosted: Wed Feb 04, 2004 3:49 am    Post subject: Reply with quote

Master

Joined: 21 Nov 2003
Posts: 265
Location: UK

Given that the BOM is not handled by the XML parser.
And if it has to be in your data. Although is not required as the data is UTF-8 and also given that you are using the MQ transport it's encoding is known.

Then you can input your message in the BLOB domain.
Remove the 3 bytes of the BOM using ESQL.
Then reparse the message in the XML domain.

This will mitigate the problem you described.
Back to top
View user's profile Send private message
martinrydman
PostPosted: Wed Feb 04, 2004 6:00 am    Post subject: Reply with quote

Centurion

Joined: 30 Jan 2004
Posts: 139
Location: Gothenburg, Sweden

Zanda,
thanks, I've got the same suggestion from other sources as well, so it definitely seems the way to go!

/Martin
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Problems with UTF-8 BOM parsing XML in WBIMB 5.0
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.