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.
Some client program outside of the EJB container must call the HOME
interface to create a reference to the Bean interface. The Bean interface
is then used to instanstate the bean. Once the bean is instantiated,
methods may be called on the bean. The client is intimately involved with
the execution of the bean. If the bean needs more information, the client
should wait for the information and call the next method when the
information arrives.
When the client that instantiated the bean dies, the bean is killed too.
The bean cannot live without a client.
So, when thinking of an EJB bean process, you should include the client as a
part of that process. And any operation that violates EJB specification can
then easly be moved from the bean back into the client.
===========================================================================
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".
