Just for your info,
I have borrowed this part from "Purple Servlet FAQ". It strongly suggests not
to put Connection object in session.
*A point I haven't seen emphasized enough is that you should only add objects
that are serializable to *an HttpSession. Specifically, a JDBC
*Connection object is not serializable, so should not be added to the session
(despite the example in *Jason Hunter's otherwise admirable Java
*Servlet Programming).
Ande Kastanis wrote:
> You may want to pack a java.sql.Connection in the user's session, use that
> connection when processing the request, and then do Connection.close() to
> stop the database processing. This is not very elegant, but it will at
> least stop the query, thus bringing a rapid end to the thread that caused
> the query to start.
>
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
