aspose file tools*
The moose likes EJB and other Java EE Technologies and the fly likes Is it problem with EJB design or with Sun's specification ?? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Is it problem with EJB design or with Sun Watch "Is it problem with EJB design or with Sun New topic
Author

Is it problem with EJB design or with Sun's specification ??

Siva Ram
Ranch Hand

Joined: Apr 04, 2002
Posts: 66
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 ??


Thanks and Regards,<br />Siva Ram .NR
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: Is it problem with EJB design or with Sun's specification ??