"lac_raz" wrote : Have tou read the singleton discussion on TheServerSide.com ?
Thanks for making me aware of this discussion. I *really* wish I had seen it before going down this path with Singletons. My original idea was to use an EntityBean instead of a Singleton, and from looking at this discussion that looks to be the concensus. Unfortunately as a new employee (and relative newbie to EJBs and JBoss) I didn't have the authority to make the design decision. And now that I've coded my application around Singletons I need to make them work, or somehow convince my manager to let me have the time to change course, which is not likely. I do (finally) have my application working well using Singletons, but it seems that a failure of the master node of my cluster will cause the Singletons to be created fresh on the new server, thereby losing the data needed by the application. Hopefully I can work this out, but really it seems that an Entity Bean approach is a much better idea. --James View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3852783#3852783 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3852783 ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
