Hello! I have a situation where a Singleton class should offer an interface to a read/write cache object. Singleton class will run in clustered environment so, I thing there would be as many Singletons as there are JVMs.
Is it ok/possible to use EntityBean or EntityBean and it's collection class member as an read/write cache object? I have thougt about following functionality: 1. EntityBean reads data from Database to e.g. a collection class (which works as a cache). 2. A Singleton class is created and is working as an interface to WebApplication (client). 3. WebApplications can read and update data that is hold in EntityBean's collection class. Singleton class provides interface for read and write actions. 4. Web Container is clustered, so there will be as many singleton classes as JVMs. So, the need is to have consistent data in EntityBean's collection class. I'm not sure if this approach is good at all..., so I would like to get tips how build a better/working solution. If someone has build same kind of solution (or better one), I would be happy to get hints/tips. Thanks, Mike =========================================================================== 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".
