Use jndi to bind it the singleton object and do lookups thereafter... I
think.
Generalize further:
"synchronized" is very forbidden when you are reading the spec. Still every
collection class is thread safe (Vector for instance). How can I be sure
that nothing will screw up one day.
Ara Abrahamian <[EMAIL PROTECTED]>@JAVA.SUN.COM> on 1999-09-23 19:50:37
Please respond to A mailing list for Enterprise JavaBeans development
<[EMAIL PROTECTED]>
Sent by: A mailing list for Enterprise JavaBeans development
<[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: EJB Restrictions-- threads, io
hi!
----- Original Message -----
From: Steve Roth <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, October 26, 1999 7:12 PM
Subject: EJB Restrictions-- threads, io
| I forgot to mention the most important restriction I've seen-- no static
| methods/data members
|
| Can U have static methods/data members?
Forbidden.
But let's generalize it more:
How can we have singleton objects?
As far as I know only entity beans and JNDI contents are shared,
session beans don't. But entities are persistent. Suppose I want
to have something like a "static activeUsersList" in a bean and act
as a true singleton object, only one instance avialable.
How can I "cleanly" implement it?
Ara Abrahamian
bi!
===========================================================================
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".
