> I think the container decides whether to maintain the
>pool of objects for a stateless bean or to serialize
>access to the bean.
>
> Vendors, any comments on how it is implemented? In
>fact, does the deployer have an option to configure
>that?
I am the container developer for the next version of EJBoss
(www.ejboss.org). In our deployment tools you can choose which kind of
pool implementation you want to use (you can also choose caching type,
distribution protocol and persistence manager through the deployment
tool, but that was not the question). One special kind of pool that we
have, which you would want to use for stateless session beans, is the
"Singleton pool". This pool only maintains one instance, making it
possible to use session beans for singleton-type functionality, yet
still having all the benefits of EJB (tx's, security, etc.). Very
useful. :-)
Note: this functionality is not yet available, but will be in the next
major version. Please come to our session at the O'Reilly conference (in
Santa Clara, March 27-30, http://conferences.oreilly.com/java/) if
you're interested.
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.dreambean.com
Question reality
===========================================================================
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".
