Laird,
We are doing something similar with a "read-only" bean to get security info out of
either an RDBMS or LDAP server. I
would suppose you would need to handle the TX programatically w/in the bean and take
the proper action "by hand" in the
LDAP tree.
-----Original Message-----
From: Laird Nelson [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 03, 2000 1:12 PM
To: [EMAIL PROTECTED]
Subject: JNDI/LDAP and transactions from within EJB container
I want to back an entity bean with a JNDI representation.
Are there any specific transactional things that I have to do with the
JNDI bits or do they work magically like DataSources do? That is,
currently if I do things with databases in an EJB world, all of the
transaction safety is implemented more or less for me (I never issue
commits, rollbacks, etc.). What must I do in the case of JNDI?
Cheers,
Laird
--
W: [EMAIL PROTECTED] / P: [EMAIL PROTECTED]
http://www.amherst.edu/~ljnelson/
Good, cheap, fast: pick two.
===========================================================================
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".
===========================================================================
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".
