On Wed, 2 Aug 2000 10:33:08 +0530, Ashwani Kalra <[EMAIL PROTECTED]>
wrote:
>according to you some of the instances in the pool can be there for which
>setSessionContext() is not called ?
Hehe.. the devil is in the details here, as usual :-)
What I said is this: before any client invoke any business method on a
stateless session bean instance, the EJB container must call
setSessionContext and ejbCreate(). How the container chooses to enforce
this is implementation specific. It *may* choose to *not* do these
invocations immediately upon instantiation, but instead defer them to
just before the first invocation of the particular instance. During the
time between instantiation and final initialization through EJB-callback
invocation, the instance may be in 1) a pool for not quite ready
instances or 2) the main instance pool but marked as "unfinished".
So, given the above, the answer to your question is Yes. BUT, this is
(as I stated very very clearly in my last post) NOT likely, as the above
implementation choice is NOT likely.
All that you as a *bean developer* (unless you wanna write your own
container, in which case the above becomes important) need to care about
is if the EJB spec is adhered to. That's all.
Do you see my point?
/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".
