Bug #46
closed
unicode character is not saved properly
Added by chin-yeh almost 14 years ago.
Updated almost 14 years ago.
Description
if the record contains non-ascii characters, for instance chinese, those characters will become ascii character instead of unicode character.
- Due date set to 11/09/2010
- Status changed from New to In Progress
the soap-adaptor module transfers all of the message in ASCII.
- Category set to JMS HornetQ
- Status changed from In Progress to Closed
- % Done changed from 0 to 100
- Resolution set to Fixed
the bug fix is available in the latest released version
Also available in: Atom
PDF