Rickard �berg wrote:
>
> > Sunil Kuchipudi wrote:
> > >
> > > Based on this premise, I do not understand why some ppl are looking to
> > > implement the singleton pattern. Please enlighten me if I am missing
> > > anything here.
> >
> > For caching read-only or read-mostly data in stateless session beans where you
> > don't want multiple copies of your cached data.
>
> <vendor>
> The jBoss EJB container allows one to use stateless session beans for
> this. A special instance pool which guarantees that only one instance of
> the bean is created can be used for exactly this purpose. This allows
> one to do singletons as an EJB, which brings all the other benefits of
> EJB, and also helps keep the application EJB only.
> </vendor>
Does the server single-thread access to the instance in this case, in case the
instances are not thread-safe?
________________________________________________________________________________
Evan Ireland Sybase EAServer Engineering [EMAIL PROTECTED]
Wellington, New Zealand +64 4 934-5856
===========================================================================
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".
