aspose file tools*
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


Win a copy of The Java EE 7 Tutorial Volume 1 or Volume 2 this week in the Java EE forum
or jQuery UI in Action in the JavaScript forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Why @Remove is optional?" Watch "Why @Remove is optional?" New topic
Author

Why @Remove is optional?

Hussein Baghdadi
clojure forum advocate
Bartender

Joined: Nov 08, 2003
Posts: 3479

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

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="http://www.sealordresortarnala.com" target="_blank" rel="nofollow">http://www.sealordresortarnala.com</a>
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Why @Remove is optional?