Re: USTRING "encoding" behavior different from STRING's?

Simon C wrote:

> The packet looks OK to me.
> 
> I think that there is a bug in the USTRING with the value keyword, it is 
> not converting to unicode internally when the value is set this way and 
> this will prevent it from being encoded when the packet is created. I'll 
> check in a fix for this later tonight and let you know.
> A possible workaround might be to encode the string you are setting data 
> to into unicode.

Simon,

Right, I just wasn't sure if this was intended behavior or not, and my current 
workaround was to encode manually, despite the 'encoding' value set.  I'll 
grab the latest code and see if it helps.

Thanks.


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642