we're currently doing this in our application. (server side singleton). provided that you are building an instance of the class using a static initializer, you shouldn't have any issues. (this also assumes that your interfaces are packaged seperately and won't be cycled on a hot-deploy).
we originally had problems b/c instead of using the static initializer, only created the instance if the instance variable was null. switching to the static initializer solved that problem and i have yet to encounter any other ill-effects. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3834320#3834320 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3834320 ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
