I see nothing wrong with mapping EBs onto LDAP for mostly read access, which is
what LDAP
is designed for. Having to connect the LDAP and obtain the data every time
without data caching
is a performance problem. I suppose one can use session beans and devise some
caching
scheme to accomplish that. However, EBs with BMP should be easier to implement.
-Jian
The problem with this is that LDAP is not a transactional resource. How
would you rollback a transaction to LDAP?
You'll have to do bean managed transactions, which I believe are only
supported for Session Beans.
Mapping EB's onto LDAP is a mistake I think.
-Chris.
> -----Original Message-----
> From: David Olivares [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, December 08, 1999 12:21 PM
> To: [EMAIL PROTECTED]
> Subject: BMP with LDAP
>
> Hi there,
> If I have a BMP Entity EJB which is persistent in LDAP (instead of a DB).
> How could I manage the LDAP connections which are context's JNDI
> connections in my EJBs...
> I see that when I load several EJB's they connect to LDAP (inside
> setEntityConext()) but they never disconnect (I am disconnecting inside
> unsetEntityConext).
> thanks
> David
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
