You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Patrick Ruckstuhl <pa...@tario.org> on 2008/08/01 12:20:53 UTC
Valid characters in strings
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Does anyone know what the valid characters for strings in map messages
are (cms)?
Thanks and Regards,
Patrick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkiS44UACgkQaA/ofYi4EMovHQCfSGOogy8SHqKbuIEQC2rVDwv3
V08An0IXu2QpjTQf+nlrBqqjvMg87Vij
=0UBT
-----END PGP SIGNATURE-----
Re: Valid characters in strings
Posted by Patrick Ruckstuhl <pa...@tario.org>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
what I find strange is that the encoding seems to work fine (so I can
send a message) but the crash happens on the receiving of a message.
The exception I get is
OpenwireStringSupport::readString - Encoding not supported
~ FILE:
activemq/connector/openwire/utils/OpenwireStringSupport.cpp, LINE: 73
~ FILE:
activemq/connector/openwire/utils/OpenwireStringSupport.cpp, LINE: 88
~ FILE:
activemq/connector/openwire/marshal/PrimitiveMapMarshaller.cpp, LINE: 361
~ FILE:
activemq/connector/openwire/marshal/PrimitiveMapMarshaller.cpp, LINE: 85
~ FILE:
activemq/connector/openwire/commands/ActiveMQMapMessage.cpp, LINE: 120
~ FILE:
activemq/connector/openwire/commands/ActiveMQMapMessage.cpp, LINE: 91
~ FILE:
activemq/connector/openwire/commands/ActiveMQMapMessage.cpp, LINE: 373
I had a quick look at the code and I'm definitely no c++ nor encoding
guru but what kind of baffled me was, that the writeString method seems
to deal with non simple ascii characters (to me it looks like it is able
to deal with at least utf8, maybe even utf16, by splitting the value
into multiple bytes). readString on the other hand seems to not (fully)
handle utf8, it reads multiple bytes but does not put them together.
Thanks for any ideas,
Patrick
| Hi Tim,
|
| is this just the "simple" ASCII set or the extended ASCII set? (e.g.
| what about umlauts?)
|
| And what it the recommended way to deal with other characters?
|
| Thanks and Regards,
| Patrick
|
|
| | The CMS MapMessage supports ASCII characters
| |
| | Regards
| | Tim.
| |
| | On Fri, 2008-08-01 at 12:20 +0200, Patrick Ruckstuhl wrote:
| | Hi,
| |
| | Does anyone know what the valid characters for strings in map messages
| | are (cms)?
| |
| | Thanks and Regards,
| | Patrick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkiWEDkACgkQaA/ofYi4EMq8TACfW64snSTjfRDh+3YqKzWMBuRN
AxcAnR8s8tOnrAOwoGp+kZm4WeNyXlRW
=YgnZ
-----END PGP SIGNATURE-----
Re: Valid characters in strings
Posted by Timothy Bish <ta...@gmail.com>.
Anything that you can put in a C++ string object should work, as far as
Unicode we don't support that and the client would throw an exception if
it received a string containing multi-byte characters. If you need to
send Unicode string data I'd recommend encoding it in a ByteMessage and
then unpacking that on either side.
Regards
Tim.
On Fri, 2008-08-01 at 16:45 +0200, Patrick Ruckstuhl wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Tim,
>
> is this just the "simple" ASCII set or the extended ASCII set? (e.g.
> what about umlauts?)
>
> And what it the recommended way to deal with other characters?
>
> Thanks and Regards,
> Patrick
>
>
> | The CMS MapMessage supports ASCII characters
> |
> | Regards
> | Tim.
> |
> | On Fri, 2008-08-01 at 12:20 +0200, Patrick Ruckstuhl wrote:
> | Hi,
> |
> | Does anyone know what the valid characters for strings in map messages
> | are (cms)?
> |
> | Thanks and Regards,
> | Patrick
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkiTIYMACgkQaA/ofYi4EMpmwwCghn/woZ86yiz+s5GCqowuHWEN
> ENAAnirE9dD8QW1ifdRRXagg+OFmwFNx
> =ss4V
> -----END PGP SIGNATURE-----
Re: Valid characters in strings
Posted by Patrick Ruckstuhl <pa...@tario.org>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Tim,
is this just the "simple" ASCII set or the extended ASCII set? (e.g.
what about umlauts?)
And what it the recommended way to deal with other characters?
Thanks and Regards,
Patrick
| The CMS MapMessage supports ASCII characters
|
| Regards
| Tim.
|
| On Fri, 2008-08-01 at 12:20 +0200, Patrick Ruckstuhl wrote:
| Hi,
|
| Does anyone know what the valid characters for strings in map messages
| are (cms)?
|
| Thanks and Regards,
| Patrick
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkiTIYMACgkQaA/ofYi4EMpmwwCghn/woZ86yiz+s5GCqowuHWEN
ENAAnirE9dD8QW1ifdRRXagg+OFmwFNx
=ss4V
-----END PGP SIGNATURE-----
Re: Valid characters in strings
Posted by Timothy Bish <ta...@gmail.com>.
The CMS MapMessage supports ASCII characters
Regards
Tim.
On Fri, 2008-08-01 at 12:20 +0200, Patrick Ruckstuhl wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> Does anyone know what the valid characters for strings in map messages
> are (cms)?
>
> Thanks and Regards,
> Patrick
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkiS44UACgkQaA/ofYi4EMovHQCfSGOogy8SHqKbuIEQC2rVDwv3
> V08An0IXu2QpjTQf+nlrBqqjvMg87Vij
> =0UBT
> -----END PGP SIGNATURE-----