Hello All,
While deploying a Stateless Session Bean , i found that the
constructor of the bean is called (I have given the no. of instances in free
pool as 5) . Also, the ejbCreate gets called for each of these instances.
I understand that when the client calls create() on the Home
Interface the call is first intercepted by the EJBHome object which then
calls ejbCreate of the Bean class. In this case, as the ejbCreate is already
called by the container while deploying the bean what happens when the
client calls create() on the Home Interface. When my client code gave a call
to the bean the business method was directly called - ejbCreate was not
called at all.
Does the container identify that being a stateless bean an
instance has already been created and that there is no need to call
ejbCreate ? If it does how does it do that?
Could some body please explain.
Thanks for the time..
Regards,
Ashutosh.
===========================================================================
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".
