| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Migration and BIP2136E |
« View previous topic :: View next topic » |
| Author |
Message
|
| JYama |
 Posted: Wed Aug 27, 2008 11:45 pm Post subject: Migration and BIP2136E |
 |
|
Master
Joined: 27 Mar 2002
Posts: 281
|
Hi all,
I have a trouble with WMB migration from V2.1 to V6.1 because the product's behavior has just a bit changed. 
I want WMB V6.x to take the same actions as before.
I know WMB V6.x has the ICU 3.2 conversion routines which detects the invalid character, "fffd" in unicode, and throws an exception (BIP2136E).
Actually in V2.1, this exception wasn't thrown.
So I want WMB V6.x to handle string fields without this exception even if it detects the invalid character.
Are there ways to achieve this? 
Many thanks in advance, |
|
| Back to top |
|
 |
| JYama |
| Posted: Thu Aug 28, 2008 4:02 pm Post subject: |
|
|
Master
Joined: 27 Mar 2002
Posts: 281
|
| Can WMB V6.x deal with substitution characters of each code page without exception BIP2136E? For example, 0xfffd in unicode and 0xf4fd in EUC. |
|
| Back to top |
|
|
| JYama |
| Posted: Mon Sep 01, 2008 3:30 am Post subject: |
|
|
Master
Joined: 27 Mar 2002
Posts: 281
|
Is it possible to handle invalid characters in XML without exception? For example substitution character 0xfffd?
Actually, I JUST want to output the substitution character in XML, 0xfffd in this case.
Is there a bypass coding in ESQL to cheat WMB not to throw the exception? |
|
| 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
|
|
|
|
