what are the limitations of the JNDIAdapter?
what are the limitations of the JNDIAdapter?
- Subject: what are the limitations of the JNDIAdapter?
- From: Benjamin J Doherty <email@hidden>
- Date: Thu, 27 Oct 2005 17:13:38 -0500
Friends,
I've been working with the JNDIAdaptor of EOF for the last few weeks,
and it works as reliably as the JDBCAdaptor. I'm now building an
application where social service agency clients are both listed as a
subclass of inetOrgPerson in a directory (so their contact
information is accessible from within Address Book on Macs, the
office webmail, Outlook, etc.) and their case data is in a relational
database. This division is mostly invisible to the users of the
application. (It's D2JC by the way.)
But there are some things that aren't the way I would want them to
be, and I'm getting a bit worn out of fumbling around with mixed
success. I'm hoping someone out there can help me determine the
boundaries of The Possible with the EOF JNDIAdaptor.
1. How can relationships work?
a. I can use the relativeDistinguishedName attribute as a foreign
key in my relational database. That's pretty exciting.
b. I don't understand whether or how I can relate directory entries
to each other. Our clients are mostly youth, and we want an
attribute that will indicate the school they attend. The schools are
also listed in our directory with objectClass organization, but
they're under a different subtree than the clients. If I use a
custom attribute with the distinguished name syntax (similar to the
"seeAlso" attribute), I can only create valid entries by adding and
stripping the search base to the attribute in my EO classes. That's
a bit clumsy. It requires hard coding the search base into my EO
classes: the RELATED entry's search base. Can't I just get a
properly distinguished name from the JNDIAdaptor?
c. Our documentation says that flattened relationships are not
possible with JNDI. That's fine with me, but I wonder if this
limitation is actually larger than flattened relationships. Can I
get to them with KVC paths?
2. What about special attributes? There are usually attributes in
directory entries that can be useful for locking, namely
modifyTimestamp. I can't access it. What I've learned is that I
need to play with the LDAP contexts' search method and specifically
name these special attributes I want to retrieve. How can I be more
specific than explicitly naming them in the model for an objectclass?
3. Can I manipulate an entry's objectclass?
a. Can I use inheritance and auxiliary classes? My experiments tell
me that I can use inheritance, which is very helpful.
b. I think that objectClass cannot be read. If the attribute is
exposed to server- or both server- and client-side EOF (remember I'm
using D2JC), the entry's EOF instance becomes unusable. It breaks
any forms based on that entity. Null values start eating up input
right after I've typed it. This happens simply by exposing the
objectclass attribute to the server-side classes.
b. How can I retrieve all the attributes from entries with auxiliary
classes?
Are there any complex examples that use JNDIAdaptor?
Thanks for any help,
Benjamin Doherty
chicago
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
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