• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: JNDI, Octet String, and UTF8
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: JNDI, Octet String, and UTF8


  • Subject: Re: JNDI, Octet String, and UTF8
  • From: Anthony Glover <email@hidden>
  • Date: Sun, 3 Oct 2004 16:36:32 -0500

According to some more documentation that I have read, the sequence "EFBFBD" is UTF-8 Hex representation of the Unicode Replacement Character. It indicates that the original Unicode character had no mapping to the local character set. So, this would indicate to me that when the EOModel via the JNDI adaptor requested the data from the server, the server thought there was no possible character mapping for some of the data and replaced it with the "Replacement Character". Any one ran into this before? Is there maybe a setting in JNDI to help with this problem?

Tony

On Oct 3, 2004, at 2:40 PM, Anthony Glover wrote:

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:
email@hidden


This email sent to email@hidden


_______________________________________________ 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
References: 
 >JNDI, Octet String, and UTF8 (From: Anthony Glover <email@hidden>)

  • Prev by Date: JNDI, Octet String, and UTF8
  • Next by Date: ssl and session management
  • Previous by thread: JNDI, Octet String, and UTF8
  • Next by thread: ssl and session management
  • Index(es):
    • Date
    • Thread