On 21 Apr 00, at 10:02, Kenneth D. Litwak wrote:
> Is there any requirement that an entity bean which is not being used at the
> moment be saved in a pool of available entity beans? I thought this was a
> vendor-specific choice and not amndated, but from something I read, I'm
> wondering if this is correct. Thanks.
Hi Ken,
No, there is no such requirement. The entity bean can remain in
the ready state. However, in the ready state, it is associated with
a specific entity object identity.
If the container does not want to keep this entity bean associated
with the object's identity, its only option is to passivate that entity
bean to the pooled state (assuming that ejbRemove was not called
by the client). From the pooled state, it can then transition the
bean to the "does not exist" state.
So specifically in answer to your question, the container does not
need to save an entity bean which is not being used in a pool of
available entity beans--but it does need to transition this bean
through the "pooled state."
This transition is required to give the bean developer a chance to
release resources.
See section 9.1.4 in the specification for more information.
-Dan
>
>
> Ken
>
> ===========================================================================
> 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".
>
------- End of forwarded message -------
===========================================================================
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".
