Thanks for your response.
I'm starting to think that my LDAP integration is non-standard and
should be done in another way. What you are suggesting is that there
might be a JCA connector for LDAP? In any case, there is nothing
vendor-specific about my current integration. I'm using a vendor-
neutral LdapConnectionFactory for obtaining a connection from a
connection pool. Perhaps I should bring the connection code into my
application instead and forget about registering the JNDI name in
GlassFish. Having a bit of difficulty finding the best practice for my
use case as you can probably sense.
You are welcome regarding the tweet. I'm planning to write a blog
entry about mixing OpenEJB, DBUnit, and Apache Derby for unit testing
in the near future as well.
Nice weekend,
Allan
On 19/06/2009, at 08.01, David Blevins wrote:
Hi Allen,
DirContext isn't one of the required java ee types such as
DataSource or UserTransaction, so I'm guessing that there must be
some sort of LDAP J2EE Connector for it. If that's the case it
should be easy to hook up in OpenEJB as well. If not then it's a
vendor specific feature, which we'd be more than happy to support as
well provided we can get enough information on how it should work so
we can code it up.
Let us know.
-David
PS Thanks for the tweet!
