The ejbCreate-will always be run if calling the home-interface's
create()-method. This is the callback from the container.
The instance of the bean-class could be cached although. (Of course, on a
per-VM-basis if running in a clustered environment.)
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Juha Lehtonen
> Sent: Monday, January 31, 2000 3:53 PM
> To: Orion-Interest
> Subject: Creation of stateless session beans
>
>
> I am using a stateless session bean,
> which should according to EJB specs
> be pooled by the container. However,
> when I create an instance of the stateless
> session bean, container (Orion) always
> calls the bean's ejbCreate. Therefore
> a new instance of a bean is created instead
> of using a pooled instance of an old bean.
>
> How can I configure the Orion server to
> handle the stateless session beans so that
> the number of new bean instances will stay
> to its minimal?
>
> Juha
>
