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 IndexWebSphere Message Broker (ACE) SupportIntegration BUS v9 - JSON Parser Issue - Help Needed

Post new topicReply to topic
Integration BUS v9 - JSON Parser Issue - Help Needed View previous topic :: View next topic
Author Message
VivekMeshram
PostPosted: Thu May 01, 2014 7:45 pm Post subject: Integration BUS v9 - JSON Parser Issue - Help Needed Reply with quote

Voyager

Joined: 25 Mar 2002
Posts: 83

Question:
How control chars like \u0003 are handled by JSON parser in IIB9.

Issue:
Web Service Provider application sends the JSON response message with control characters (e.g.\u0003) escaped as per JSON specification but when JSON Parser domain is used in IIB9, it outputs as hex chars (e.g. [0x3] ). JSON parser escapes all other special characters (/,\,” etc) except the control chars.

Assistance Required: What is workable solution for this scenario.

Appreciate help.
Thanks,
Vivek
Back to top
View user's profile Send private message Send e-mail
fjb_saper
PostPosted: Thu May 01, 2014 7:58 pm Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

wouldn't the right escape sequence be "\\u003"?
Notice that with "\u003" it is the u character that is escaped...
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
stoney
PostPosted: Thu May 01, 2014 11:15 pm Post subject: Reply with quote

Centurion

Joined: 03 Apr 2013
Posts: 140

This is a defect in the JSON serializer - only certain characters get escaped on output (currently \", \\, \/, \b, \f, \n, \r and \t). Can you raise a PMR for this issue and include a link to this thread please?

Alternatively, you could find and replace all of the 0x00-0x1F control characters with the appropriate escape sequence (\u00xx) before the message is serialized.
Back to top
View user's profile Send private message
VivekMeshram
PostPosted: Sun May 04, 2014 9:50 pm Post subject: Reply with quote

Voyager

Joined: 25 Mar 2002
Posts: 83

Thanks Guys!

We have raised a PMR and IBM is looking in to it. In the meantime, we are also replacing the values but was afraid that using multiple REPLACE functions could you affect the performance.

Regards,
Vivek.
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexWebSphere Message Broker (ACE) SupportIntegration BUS v9 - JSON Parser Issue - Help Needed
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.