File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes EJB and other Java EE Technologies and the fly likes Why @Remove is optional? 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 "Why @Remove is optional?" Watch "Why @Remove is optional?" New topic

Why @Remove is optional?

Hussein Baghdadi
clojure forum advocate

Joined: Nov 08, 2003
Posts: 3479

Why EJB 3 specification marked @Remove annotation as optional for stateful session beans although it is so important and vital for the EJB container?
Gladwin Burboz

Joined: Feb 26, 2008
Posts: 25
Stateful or stateless is just EJB configuration option. Underlying bean still implements same "javax.ejb.SessionBean" interface. For bean implementing this interface, remove() method is optional and so is annotation.

<a href="" target="_blank" rel="nofollow"></a>
I agree. Here's the link:
subject: Why @Remove is optional?
It's not a secret anymore!