Of course, Chapter 18 contradicts this by saying that the container must not call any call back methods when discarding an instance due to an system exception. However, section 18.3.7 states that all resources obtained from resource factories declared in the bean environment must be released. Maybe that will help.
Otherwise, you'll have to catch all runtime exceptions and releaes your resources before rethrowing. --Victor Victor Langelo wrote: > Anamitra, > > According to the 2.0 spec, the only state transition from the method > ready pool to does not exist state requires that the ejbRemove method be > called. So your ejb container does not comply with the spec. Section > 7.8.3 explicitly states that exceptions result in the transition to the > does not exist state. > > --Victor > > =========================================================================== > To unsubscribe, send email to [EMAIL PROTECTED] and include in the > body > of the message "signoff EJB-INTEREST". For general help, send email to > [EMAIL PROTECTED] and include in the body of the message "help". > =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
