My intention was that the instance must be "loaded" before ejbRemove
is called. This means that ejbLoad would be called in your below scenario.
I think that allowing the container not to call the ejbLoad would
lead to an error-prone programming model for the developer of the
ejbRemove method. This is because sometimes the instance
would be "loaded", and sometimes it would not.
Requiring the ejbLoad method is also necessary to make the
BMP model consistent with CMP.
I will try to make this clear in the spec.
Vlada
----- Original Message -----
From: Chip Wilson <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, June 18, 1999 5:48 AM
Subject: Re: FW: ejbRemove without ejbLoad?
> Thanks Vlada, but that doesn't quite clear it up.
>
> ejbCreate will essentially load the bean, since it is required to set the
> bean's instance variables before returning. With BMP, these are the same
> instance variables that ejbLoad sets. In the spec, these instance variables
> are called the beans "cached state".
>
> Let me restate:
>
> Is it a valid state transition for an entity bean with BMP to go from pooled
> to ready with a call to ejbActivate, and then immediately back to pooled
> with a call to ejbRemove, without ejbCreate or ejbLoad being called by the
> container?
>
> Another way to state this is:
>
> Should ejbRemove on an entity with BMP be coded to only depend on the
> primary key in the entity context, or can it assume that its other instance
> variables (cached state) have been set by either ejbLoad or ejbCreate?
>
> > -----Original Message-----
> > From: Vlada Matena [SMTP:[EMAIL PROTECTED]]
> > Sent: Thursday, June 17, 1999 7:17 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: FW: ejbRemove without ejbLoad?
> >
> > There is no guarantee that an ejbLoad is called before ejbRemove. For
> > example,
> > an instance may not receive an ejbLoad if the instance got to the "ready"
> > state via
> > the ejbCreate/ejbPostCreate transition.
> >
> > Vlada
> >
> > ----- Original Message -----
> > From: Chip Wilson <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Thursday, June 17, 1999 3:58 PM
> > Subject: FW: ejbRemove without ejbLoad?
> >
> >
> > > Actually, the question is even more important for entities with bean
> > managed
> > > persistence. Should entities using BMP implement their ejbRemove
> > methods
> > > depending only on their PK from their EntityContext, or can they assume
> > they
> > > have been loaded (ejbLoad)?
> > >
> > > > -----Original Message-----
> > > > From: Chip Wilson
> > > > Sent: Thursday, June 17, 1999 4:32 PM
> > > > To: '[EMAIL PROTECTED]'
> > > > Subject: ejbRemove without ejbLoad?
> > > >
> > > > Is it allowed for a container to call ejbRemove on an entity bean with
> > > > container managed persistence without ever having called ejbLoad on
> > the
> > > > instance?
> > > >
> > > > Chip Wilson
> > > > ObjectSpace
> > > >
> > >
> > >
> > ==========================================================================
> > =
> > > 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".
> >
>
> ===========================================================================
> 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".
