I assume this only works when there is a single server JVM?
-Chris.
> -----Original Message-----
> From: Rickard �berg [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, May 31, 2000 9:08 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Singleton design/implementation techniques
>
> > > <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?
>
> <vendor>
> Yes. The EJB semantics are preserved. It behaves the same way as an
> ordinary stateless session bean, but with the addition that the pool
> only contain at most one instance which is synchronized.
> </vendor>
>
> It's perhaps not a perfect solution (although I can't think of any cons
> right now), but should be good enough for most situations.
>
> /Rickard
>
> --
> Rickard �berg
>
> @home: +46 13 177937
> Email: [EMAIL PROTECTED]
> http://www.telkel.com
> http://www.jboss.org
> http://www.dreambean.com
>
> ==========================================================================
> =
> 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".
===========================================================================
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".
