On Tue, 1 Aug 2000 11:13:10 +0530, Ashwani Kalra <[EMAIL PROTECTED]>
wrote:
>You are right,
>But I wanted to emphasize that no of EJB create call may not coincide with
>the no of instances in the pool as one instance can service many calls.
That is both true and not true. The rule is that prior to any client
invocation the container must have called setSessionContext and
ejbCreate. If the container implementor chooses to keep bean instances
in the pool on which these two methods have not been called, then you
are correct, just as long as the container keeps track of this and makes
sure that these EJB callbacks are invoked prior to the use of any
instance.
However, the *likely* implementation is that these methods are called
immediately (since it is much easier to do). If this is the case then
the number of instantiations, setSessionContext calls, and ejbCreate
calls will be equal.
So, while you are correct from a EJB spec point of view, I would argue
that in practice this will rarely occur due to the likelyhood that the
implementation uses the easiest approach to implementing the EJB spec.
/Rickard
--
Rickard Öberg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
===========================================================================
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".
