This week's giveaway is in the Android forum.
We're giving away four copies of Android Security Essentials Live Lessons and have Godfrey Nolan on-line!
See this thread for details.
The moose likes EJB and other Java EE Technologies and the fly likes Steteful Session beans without Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Java » EJB and other Java EE Technologies
Bookmark "Steteful Session beans without "@Remove"" Watch "Steteful Session beans without "@Remove"" New topic
Author

Steteful Session beans without "@Remove"

Sol Mayer-Orn
Ranch Hand

Joined: Nov 13, 2002
Posts: 311
I'm new to ejb3.
I've noticed that the spec doesn't force you to define a "@Remove" method on a stateful Session bean...

I was wondering:

1. Is it considered a legitimate design choice, to have a Stateful Session bean without 'Remove' ? Or is it a bad sloppy design (like, for example, programmers who obtain a direct SQL connection from an Oracel DataSource, and they don't bother close the connection because they rely on the Oracel DataSource configuration to automatically clear such connections after a timeout: this works, but it's consdered a very sloppy approach).


2. Does the spec guarantee that such beans will be removed automatically after some "session timeout" ?

thanks a lot
[ September 25, 2007: Message edited by: Sol Mayer-Orn ]
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Steteful Session beans without "@Remove"
 
Similar Threads
My SCEA Part 1Study Notes
Access and meaningful transaction context
Release resource in @remove method
Transaction Exception and NoSuchObjectException
There can be only one Stateful Session Bean per EJB Client