Passing Connection to Another Thread

Question

I have an email blasting POJO that is used to notify interested members when new content is posted on our site. This may involve sending a couple hundred emails (as I don't want one email with several hundred receipients) so I have it threaded. It pulls email address information from the user database, so I pass it the a connection from our pool.
As this thread now has this connection, I don't close it from the originating class that created it, as it may still be in use (correct?) so instead I have the threaded mailer close it.
Does this sound clean or is there a better way to do this?

Answer 1

But i am not sure how do u read the values from the
resultSet return from the super class as it will
close the connection object. Well once the connection
object is closed the resultset is also closed isnt
it??
Please enlighten us how did you do it in your
project. Ofcourse it would.
**sigh** dint i mention it was pseudo code ?
You dont tamper with ResultSets outside the DAO, period. You do not
pass data back to the caller (be that your sub DAO classes or your front
end handlers/servlets/jsps) .
To the super class DAOManager, a model class and a Map is passed.
The DAOManager class populates the specified model object from a
resultset. The map contains the mapping from database column
names to the properties in the model object. The key of the
modelObjectMap is the database column name and the value is the
name of the property in the model object. Properties in the model
object are mapped according to the mapping suggested by JDBC 2.1
API.
Thus the code would be
public List executeQuery(String sqlString, List bindValues,
            Class a_class, Map dbModelMap){
            Connection dbConnection = getConnection();
            String sql = prepareSql(sqlString, bindValues); //private method
//that binds the values to the raw sql string and creates a prepared
//statement
             ResultSet results = executeQuery(); //private method again that
//executes the prepared staement object.
             return getObjectResults(results, a_class, dbModelMap);
              //close result sets, connections etc in finally
private List getObjectResults (results, a_class, dbModelMap){
             //for each result set iteration{
                    //create an instance of a_class
                    //lookup the map - for each column, find the corresponding
//attribute in the class, using reflection, call the setter methods for
//the column value
                    //add the instance to a list
             //return list
}I dint post this initially because I have seen enough of linxpda's posts
to know that he would have grasped the essentials quickly enough.
I dint account for the others who may happen to read this post - I stand
corrected.
cheers,
ram.