If you are using bean managed persistence, then all of the database access
code is normal jdbc stuff.
We need our system to run on EJB and non-EJB platforms, so I am wondering
whether I can put all of the database access coed into a seperate class, and
delegate to this class from my entity beans.
I know this will compile, deploy and run, but what afect, if any, does it
have on container managed transactions?
TIA
Phil Lewis
Chief Designer
Knowledge Management Software plc
Any opinions expressed in this email are those of the individual and not necessarily
Knowledge Management Software plc. This email and any files transmitted with it are
confidential and solely for the use of the intended recipient.
If you are not the intended recipient or the person responsible for delivering to the
intended recipient, be advised that you have received this email in error and that any
use is strictly prohibited. If you have received this email in error please notify
the Systems Manager by telephone on 44 (0) 161 227 9009
===========================================================================
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".
