What should I do if I need a singleton?

[Maria Soledad Escobar - Sun Argentina]

Hi all!!!
Say you want a stateful, shared, server-side object, i.e., a singleton.
EJB
does not provide this design pattern explicitly. I could use an entity
bean,
but these are really intended to be stored in either a database or some
(other) legacy backend. Writing a stand-alone entity bean (which
provides
full transactional semantics, as entities should) is overkill for a
simple
singleton. Or, you could use a stateful session bean, but these are
intended
to be single-user. (In reality, it is not possible for a container to
enforce this rule, and thus it could be ignored, but again we find
ourselves
doing something quite unnatural in EJB.)

any suggestions?
Thank you :-)

--
         ______
        /_____/\          Maria Soledad Escobar
       /____ \\ \         Systems Engineer
      /_____\ \\ /
     /_____/ \/ / /       Sun Microsystem de Argentina
    /_____/ /   \//\      Bouchard 547 Piso 26
    \_____\//\   / /      Buenos Aires (1106)
     \_____/ / /\ /       Tel: (54) 11-4317-5600
      \_____/ \\ \        Fax: (54) 11-4311-8999
       \_____\ \\
        \_____\/

===========================================================================
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".