For ejbLoad() and ejbStore() in a CMP bean, I meant using these methods only
to 'fix-up' bean attributes for persistence by the container - not to add in
additional jdbc operations. I do not think that will work.
Unless a special provision is provided in the app server, your connection
for additional jdbc operations would likely not be in the same transactional
context. I think this is prety far out of the spec at this point.
- Dan
-----Original Message-----
From: A mailing list for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED]]On Behalf Of Christopher Cobb
Sent: Monday, November 20, 2000 11: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".
