ok, it might be that the java sender is actually sending a string, and not a bytearray. Will check this later today, and get back.
btw: is there utf8, unicode or wstring planned ? Søren Timothy Bish wrote: > > On Mon, 2008-10-06 at 03:46 -0700, Sodan wrote: >> Btw, I cant even do map->getBytes ... >> >> but why would it do exception in the first place, when reading the long ? > > You would see this on the first read because the Message Properties are > unmarshalled lazily since many users don't even access them this way > message are delivered faster. The first access is causing the > properties payload to be unmarshalled and the bytes you are setting are > apparently being interpreted as a string which sounds like a bug, > although without sample code its hard to say for sure. > > You could create a JIRA issue and attach a Java sample app and c++ > sample that demonstrate what you are doing. That way the problem will > be captured and someone can take a look at it as soon as possible. > > Regards > Tim. > > > -- View this message in context: http://www.nabble.com/%27readString---Encoding-not-supported%27-exception-%28-ActiveMQ-CPP-%29-tp19827735p19837451.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
