Seems like a natural thing to use ejbLoad and ejbStore in a CMP bean. But
the EJB spec 9.4.1 says "An entity bean with container managed persistence
must not code explicit data access - all data access must be deferred to the
container." Of course most containers do not enforce this.
Unless you get a connection from the container you will have transaction
issues, because your JDBC will not be in the same transaction as the rest of
your enity bean data access.
Rick Hansen
-----Original Message-----
From: Christopher Cobb [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 20, 2000 10:42 AM
To: [EMAIL PROTECTED]
Subject: Re: Entity and Dependent
Dan Weimer wrote:
> If you really, really want to use CMP with a dependent object in an entity
> bean, consider the following steps.
>
> ...
>
> In other words, use ejbLoad and ejbStore to transform the dependent object
> into a form compatible with weblogic's simple container managed
persistence
> capability.
My dependent object is already a subservient table. How bad would it be to
make JDBC calls to that table myself instead of serializing. I was thinking
that ejbLoad and ejbStore should probably not be used with CMP -- but if I'm
going to use them, I'd probably tend to want to use JDBC. Are there
'transactional' reasons not to use my own JDBC calls within a transactional
bean?
cc
===========================================================================
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".
