Tim Tye wrote:
> There seems to be a lot of confusion on this list about the way in which EJB
> beans start their existance.
> Some people seem to think that (all?) EJB beans are automagically started
> when the container is started. This is simply not true. When the container
> is started, the EJB beans are loaded, but only the HOME interface is
> started.
It's even more subtle than that. When the container is started, it may be
that nothing happens at all. It may be that no EJB homes are instantiated
or activated until a client looks one up via JNDI and sends a message to
the resulting stub. It may be that EJB bean classes are loaded on demand,
and that instances are created on demand.
But you're right that in general the clients are the ones that initiate
most activities.
Marc San Soucie
GemStone Systems, Inc.
Beaverton, Oregon
[EMAIL PROTECTED]
===========================================================================
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".
