RFC 5020 is trying to fix this, adding a virtual entryDN attribute : http://www.rfc-editor.org/rfc/rfc5020.txt
That's not a bad idea. However, I don't know whay using a DN in the requetsed attributes should automatically lead to an error. Is there a major problem forbiding a server to return a DN as if it were an attribute, if specifically requested ? On Mon, Feb 23, 2009 at 11:23 AM, ayyagarikiran <[email protected]> wrote: > I believe the jabber server's LDAP setting is treating the 'dn' as a > attribute name (e.x the attribute used for fetching the uid or group value > ). > > btw, are you using openfire? > > Kiran Ayyagari > > Yiannis Mavroukakis wrote: >> >> Hello Emmanuel, >> >> I ended up using Ldiff Entry and it works like a charm! Now the issue is >> with a jabber server I have connecting to ApacheDS. I am getting a lot of >> this in the logs >> >> 10:04:12,027 WARN [SearchingOperationContext] Requested attribute dn does >> not exist in the schema, it will be ignored >> >> In response to this request from the Jabber server >> >> 2009-02-23 10:04:12,074 DEBUG >> [org.apache.directory.shared.ldap.codec.TwixDecoder] Decoded LdapMessage : >> LdapMessage >> message Id : 13 >> Search Request >> Base Object : '' >> Scope : base object >> Deref Aliases : never Deref Aliases >> Size Limit : no limit >> Time Limit : no limit >> Types Only : true >> Filter : '(objectclass=*)' >> Attributes : dn >> >> I googled around for this but could not find a satisfactory answer, anyone >> have any ideas? >> >> Thank you, >> Yiannis >> >> Emmanuel Lecharny wrote: >>> >>> On Fri, Feb 20, 2009 at 5:04 PM, Yiannis Mavroukakis >>> <[email protected]> wrote: >>> >>>> >>>> Hello Emmanuel, >>>> >>>> I tried the procedure you described (getEntry() ) but read/writeExternal >>>> are >>>> both setup to throw exceptions, and the messaging layer >>>> I am using is using those methods to marshall and unmarshall the >>>> objects. I >>>> did see that DefaultServerEntry has serialize/deserialize methods >>>> but because it's final, I cannot subclass it, and call these methods >>>> from >>>> within my subclass' read/writeExternal.... >>>> >>> >>> You have the ServerEntrySerializer class, which is way better as it >>> serializes/deserializes the Entry the best possible way, using an >>> internal serialization, instead of the default Java serialization. >>> >>> Give it a try. >>> >>> ( you can check the ServerEntrySerializerTest for an exemple on how to >>> use it). >>> >> > -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
