Is it problem with EJB design or with Sun's specification ??
posted 14 years ago
Hi all, If we are using entity bean / Stateful session bean , if the ejb passivation is called, it should automatically destroy the the entity instance ..( By removing the particular instance in finalize block) If it has been done in EJB 2.0 , then it will be easy for Java world itself. Instead if the exception happens, even though passivate method is called internally the resources used by the bean are not released. We have to explicitly to do this ?? Is it the problem with EJB design patterns made by experts or Sun Spec fault ??