JDBC connection in session using HttpSessionBindingListener

Question

Hi All,
Our architechture needs us to store an OCI connection in the HTTPSession once
the user logs in. This connection is then used for any DB related queries(passed
around to workshop controls etc). I know this is againt generally recommended
practice, but given that we need to do it, i thought of wrapping this connection
in an HttpSessionBindingListener ,so that when the Servlet API calls the onValueUnbound(),
i can close the internal connection. However, it has come to my notice that the
valueUnbound method is not called each and every time a browser window is closed
or a session times out. Does my wrapper object NEED to implement Serializable?Even
if it does, the internal OracleOCIConnection is still unserializable. Is there
any way i can close such a connection reliably when session is closed/invalidated/expired?
Thanks.
Vik.

Answer 1

Hi, I'd refer you to the ejb newsgroup for expert help in that
area. I'm jdbc, and what you wanted sounded like that.
Joe
vik wrote:
Joe,
If we were to use a Statefull session bean to do this, could you guide me on how
i would go about doing it in general terms? One way i can think of is:have a ejbCreate(userName,passWord),
which is called on login. This calls the getConnection(userName,passWord) from
the connectionPool,and if the username/pwd is invalid, i will get a CreateException
wrapping a SQLException. If it goes allright, i now have a session bean associated
with this client holding a JDBC connection using his credentials.How would i share
this session bean across the app so that if there are any SQL operations to be
performed by any action(we are using WorkShop and Weblogic8.1), they are done
using this session bean. Should i be storing this Stateful Session Bean in the
HTTP session then?
Regards,
Vikram.
Joe Weinstein <[email protected]> wrote:
vik wrote:
Hi All,
Our architechture needs us to store an OCI connection in the HTTPSessiononce
the user logs in. This connection is then used for any DB related queries(passed
around to workshop controls etc). I know this is againt generally recommended
practice, but given that we need to do it, i thought of wrapping thisconnection
in an HttpSessionBindingListener ,so that when the Servlet API callsthe onValueUnbound(),
i can close the internal connection. However, it has come to my noticethat the
valueUnbound method is not called each and every time a browser windowis closed
or a session times out. Does my wrapper object NEED to implement Serializable?Even
if it does, the internal OracleOCIConnection is still unserializable.Is there
any way i can close such a connection reliably when session is closed/invalidated/expired?
Thanks.
Vik.This sounds like stateful session bean, no?
Joe