Description of problem:
This bug is in reference to the new messaging APIs.
The handling of strings is different between the C++ and Python messaging APIs.
The Python API assumes strings on-the-wire are UTF-8 encoded. The C++ API
apparently uses raw, unencoded octet arrays.
If a binary string of octets (with some octets > 0x7F), is encoded by a C++
client and received by a Python client, the Python client will throw an
Version-Release number of selected component (if applicable):
SVN revision 924529 and prior.
Steps to Reproduce:
1. Use the C++ API (qpid::messaging) to produce a map-message (using
MapContent). One of the map entries should have a string value and should
contain a sequence such as "!E\xf9\xf5\xdf\x89d\x011\xc0\xc8$7H\x99T"
2. Use the python client to receive the message.
The Python client will throw an exception when it tries to UTF8-decode the
Either Python should use raw-octet encoding or C++ should use UTF8. I expect
the string seen by the Python receiver to be identical to that sent by the C++
|Field||Original Value||New Value|
|Assignee||Gordon Sim [ gsim ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|19h 59m||1||Gordon Sim||18/Mar/10 18:42|
|1229d 11m||1||Justin Ross||29/Jul/13 18:54|