JNDI, Octet String, and UTF8
JNDI, Octet String, and UTF8
- Subject: JNDI, Octet String, and UTF8
- From: Anthony Glover <email@hidden>
- Date: Sun, 3 Oct 2004 14:40:05 -0500
I'm retrieving some data from an ADS server via an EOModel. The field
that I am retrieving (objectGUID) is binary. According to the ADS
documentation it is an Octet String. The data is supposed to be 16
bytes long. After I reverse engineer the schema using EOModel and view
the data in the field of interest, it appears to be somewhat garbled.
For example one value is supposed to be:
65 AC 62 8D ED A0 4D 05 99 B5 42 16 4B 71 78 22
The value returned by the EO framework/model is this:
EF BF BD 62 EF BF BD 65 EF BF BD EF BF BD 05 4D EF BF BD EF BF BD 42 16
4B 71 78 22
The pattern "EF BF BD" appears to be replacing some of my hex pairs,
e.g. if I replace that pattern with just some dummy "XX"s, then I get:
XX 62 XX 65 XX XX 05 4D XX XX 42 16 4B 71 78 22
Even though the numbers are swapped around a bit, at least is is 16
bytes long this way. I get one set of "EF BF BD" for each missing pair.
After doing some searching, the pattern EFBFBD seems to be some sort of
UTF8 encoding signature. Does anyone have any ideas as to why I would
be getting this back from my JNDI/LDAP queries?
Thanks,
Tony
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden