David Michaels wrote:
> Can you guys explain to me how this singleton idea works? Since session
> beans are not shared between simultaneous clients, I dont see how I can
> create just ONE of these for all clients to talk to - wouldn't multiple
> copies get created? I do want one of these per VM, but I don't think
> thats an issue since I'm using Weblogic and they pretty much keep
> everything in one VM as I understand.
>
> So is the singleton a class, (with static members, presumably against
> the EJB spec) or a bean, or what?
>
> I'm perplexed how this idea hasn't come up before - it seems to be an
> obvious thing to need to do (to cache data in the business logic layer
> so as to reduce load on the database (the central bottleneck)
>
> thanks!
>
> David
If you check the archives, you will see a number of discussions on 'singleton'.
The Cliff Notes version of the discussion is this: it is not possible within EJB
beans. So how do you it? Depending on you poison preference, either an RMI or
CORBA object bound into your JNDI (depending on vendor) tree would suffice for a
singleton object. There is no law that says that you cannot mix distributed
object environments.
--
Perry Hoekstra
---
"I don't see much sense in that," said Rabbit.
"No," said Pooh humbly, "there isn't. But there was going to be when I began it.
It's just that something happened to it along the way."
===========================================================================
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".
