A quick work-around until they fix the bug would be to put TX_REQUIRED on
every method (even those not actually being quite transactional).
> -----Original Message-----
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Chip Wilson
> Sent: Saturday, December 04, 1999 5:55 PM
> To: [EMAIL PROTECTED]
> Subject: Re: J2EE and BMP Initialization
>
>
> I have not used the RI, but have seen this behavior in other app
> servers. There
> is a misconception among the server vendors that ejbLoad only
> needs to be called
> when a transaction is started. This position is clearly
> incorrect and is not
> supported by the spec. All the servers I have used have
> corrected this bug, but
> it sounds like it crept into the RI. I would try posting on that
> list for help.
>
> Joseph Ess wrote:
>
> > I am using the J2EE to design a prototype application. The
> problem I've run
> > into is that entity beans (using BMP) are not getting
> initialized properly.
> > The documentation (and serveral posts to this discussion) state that the
> > container calls ejbActivate to associate a bean with the
> database and then
> > calls ejbLoad to load the data. The entity beans I am using are having
> > ejbActivate called, but not ejbLoad. The result is that any
> session bean or
> > client that tries to use the entity beans receive null data. Has anyone
> > else encountered this behavior?
>
===========================================================================
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".
