Should calling EJBObject.remove() on a SFSB which has been removed already throw an exception or should the request be silently ignored?
I was running into a problem which was due to one of my finializers removing a SFSB, which I had previously removed and forgot to null. Currently when this happens an erronious activation exception is thrown, since there is no state file for the bean (having been removed already). I think it would be a good idea to throw a meaningful exception in StatefulSessionContainer.remove() to indicate the illegal state... unless the spec says we should ignore this. I have not checked the spec. The Javadoc for EJBObject.remove() does not provide any insight either. Does anyone know what the behavior should be, exception or non-exception? And if it is an exception what flavor? --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
