What about using an Entity bean but persisting to a file instead of a
relational or object database. I think you have to go with an Entity bean on
this one, making a new bean type just to support singleton seems like
overkill.
-----Original Message-----
From: Eric Yu [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 15, 1999 9:01 AM
To: [EMAIL PROTECTED]
Subject: Re: Shared EJBs
It seems the original intent of this query (and the one in the thread on
"Static variables in EJB") is to implement a singleton-type of bean. Given
that session beans are not sharable, EJBs in general don't support mutable
statics, and implementing it as an entity bean seems somewhat kludgy (in
that there may be no persistent state or primary key), should this singleton
not even be an EJBean?
....
===========================================================================
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".
