I am not sure exactly what you are doing here, but you might want to just use a shared connection pool rather than having a connection for each session. Even if you could close the connections when the session ends, leaving those connections open throughout a session probably isn't the best idea unless they are constantly being used.
Travis ---- Original Message ---- From: Andrew Vardeman <[EMAIL PROTECTED]> Sent: 2002-05-10 To: [EMAIL PROTECTED] Subject: RE: stateful service example (no cookies) Replying to myself because I realized I was misunderstanding the JSP/servlet version of things. Still, what it all comes down to is that I have objects I want to have session scope, but I want to be able to explicitly "destroy" them before they are simply unbound when the session object times out. Andrew At 03:59 PM 5/10/2002 -0500, you wrote: >Glen, > >Thanks again for the info. I have one more question regarding the >Axis-provided session maintenance that I was hoping someone could answer: > >In JSP/Servlets, a javax.servlet.http.HttpSession object "[calls] the >valueUnbound() method of all objects in the session implementing the >HttpSessionBindingListener interface." Does an >org.apache.axis.session.Session do something similar? I'd like to use >this built-in functionality, but mostly for storing jdbc Connection >objects, and I would really like an opportunity to call the close() >methods on these when a session times out. > >Andrew
