I am designing a java class (API) that keeps track of number of times certain evets happen in EJB container. Primary concern is this collected data should not be persistent(for efficiency purposes). And this collected data will be sweeped by polling modules periodically.
If more than one instance of an EJB is updating this collector instance there are sync problems, so I wish I can utilize container managed concurrency.... Is this possible without persistence, or is there any singleton object than can reside inside a container... or you would say JMS store, oh no.. just simple programmable thing.
Thanks,
Srini
-
pls help with a good design pattern (3 messages)
- Posted by: Srinivas Pittala
- Posted on: January 04 2002 15:03 EST
Threaded Messages (3)
- pls help with a good design pattern by Tom Davies on January 06 2002 18:06 EST
- pls help with a good design pattern by manoj sharma on January 08 2002 06:36 EST
- pls help with a good design pattern by Srinivas Pittala on January 08 2002 03:09 EST
- pls help with a good design pattern by manoj sharma on January 08 2002 06:36 EST
-
pls help with a good design pattern[ Go to top ]
- Posted by: Tom Davies
- Posted on: January 06 2002 18:06 EST
- in response to Srinivas Pittala
Why not just synchronize the update methods?
Tom -
pls help with a good design pattern[ Go to top ]
- Posted by: manoj sharma
- Posted on: January 08 2002 06:36 EST
- in response to Tom Davies
Do u mean sysnchronising the updates !! what about performance then ??
MaX -
pls help with a good design pattern[ Go to top ]
- Posted by: Srinivas Pittala
- Posted on: January 08 2002 15:09 EST
- in response to manoj sharma
Thanks Tom,
That helps, I donot earlier that we can use synchronized in EJB. Confused with what to use and what not to in the container...
bye
srini