Hello,
I post below an answer that I already sent to another mailing list.
One of the problems with entity beans persistent support, is its
integration with the EJB server transaction management.
This is currently done through the Datasource
object: each time you call the getConnection method of the datasource
object, the XA resource (of the persistence support) is attached to the
current transaction (managed by the Transaction Manager of the EJB
server), each time you close this connection, the transaction and the
XA resource are dissociated ... The transaction manager is thus aware
of the XA resources involved in a transaction, and may
prepare/commit/rollback this transaction on the different persistence
supports (and also on other XA resources such as JMS ones ...).
In other words, your persistent support must be "transaction aware",
which is not the case of most LDAP implementations, and more,
it must be XA aware, so that transactions can be handled by the
transaction manager of the EJB server.
At the moment, only one persistence support exposes such
transactional properties to an EJB server : the "JDBC databases".
We are currently investigating on how to integrate other persistence
supports, files, ldap, proprietary enterprise systems, ... It appears
that the most appropriate way should be to use the j2ee Connector
Architecture, which generalizes the current "Datasource/XA" approach
to integrate the Transaction/security/pool management of the external
information system (persistent support in our case) with that of the
application server. This is what is currently done in collaboration with
an Objectweb partner to enhance the JOnAS persistence management (EJB
2.0 persistence aspects, different persistence supports).
Persisting entity beans in LDAP was one of the first subject of
interest at the beginning of JOnAS, and I remember some prototypes
where it was possible to define an "LDAP datasource" with a getContext
method ! ... However the use of such entity beans was limited, not
standard, and we were always faced to the lack of transactions in
LDAP ...
If you don't have to write in your LDAP directory, you may develop
session beans that perform your LDAP operations ?
Best Regards,
François
jayashree wrote:
> Hi,
> Does Jonas provide support for LDAP?
> If we have to use LDAP based directory service( like - Netscape Directory
> server)
> instead of a database, how should we go about it?
> Can I use the netscape sdk for LDAP and make connection to LDAP serer from
> entity bean?
> Or do I have to use JNDI for looking up a LDAP server?
> please help.
>
> Thanks,
> Jayashree
>
> ----
> To unsubscribe, send email to [EMAIL PROTECTED] and
> include in the body of the message "unsubscribe jonas-users".
> For general help, send email to [EMAIL PROTECTED] and
> include in the body of the message "help".
--
==================================================================
Francois EXERTIER Evidian (Groupe Bull)
1, rue de Provence, BP 208, 38432 Echirolles cedex, FRANCE
mailto:[EMAIL PROTECTED]
http://www.evidian.com/jonas http://www.objectweb.org/jonas
Tel: +33 (0)4 76 29 71 51 - Fax: +33 (0)4 76 29 76 00
==================================================================
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
