> I agree, best that the EJB spec allows, as flawed as this is.
>
> I see the problem with this design is; performance (lack of).
> Serialized calls to a singleton is ... not acceptable. How can this
> be so easily over looked and shrugged off??? Maybe because there's
> so many short commings that how can we get upset over just the Singleton
> problem?
Mm... a challenge :-) Irresistable.
<vendor>
I have added an option to the previously mentioned singleton feature
which allows the deployer to select whether calls to the singleton
instance should be synchronized or not. I have also added
configurability in the deployment GUI for this option.
If synch. is off the performance of usage of singletons is improved, but
the bean writer must take care so that concurrent use is really
supported. Read-only state is preferred.
jBoss users can pick up this new feature from the CVS repository.
</vendor>
:-),
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".
