Javier Borrajo wrote:
> If the data is read-only and does not need to be persistent,
> you could implement a singleton repository that provides public
> static methods to get at the shared read-only data.
>
> I don't see the need for transactions, persistence or security here.
>
> This singleton repository would be local and available to all
> EJBs in the same container.
In some EJB architectures your beans may be distributed among a number
of distinct Java VMs, possibly on more than one physical machine. The
singleton will have to be remotely accessible if the contents are to
be globally shared. If it's purely read-only, you could establish one
singleton per VM, though getting to it may be an issue.
There is also the question of securing the data, if it needs securing.
Marc San Soucie
GemStone Systems, Inc.
===========================================================================
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".
