I am wondering if this is the case, if an EJB's name will be unique across all other bean's deployed in the vm... or if the name only has to be unique inside of a ejb-jar deployment.
The current file-based SFSBPM uses the bean's name to determine the directory to store session state files. If it is not unique then two SFSB beans with the same name could collide here... or rather when the second bean container is started, the PM will erase any state files in the storage directory, which means that any passivated beans from the first container are now screwed. The fix is easy, but I am not sure if it is needed. Anyone know? --jason _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
