Hi A simple question of Yes/No. In case my application targets clustering in future, is it O K to use writable singleton classes in the ear?
There is a case here when a singleton's properties are modified at run time. Of course this modification dictates further bahaviour of the application. I am wondering, because clustered servers run in different JVMs, wud it result in separate instances of the singleton for different JVMs? (which though does not affect read-only cases, becomes an issue here) So, the question is, whether clustering tackles this issue or shud I avoid writable singletons in my application? --- Pooja <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3826822#3826822";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3826822>Reply to the post</a> ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
