Hello All,
I'm a longtime Tomcat user/tweaker, new Axis user. I must say I've been so far impressed with the ease of use, especially for someone who's already familiar with J2EE development.
Out of the box, it looks like Axis supports sessions through a combination of:
org.apache.axis.handlers.SimpleAuthenticationHandler org.apache.axis.handlers.SimpleSessionHandler
For services deployed with session scope, this gives you access to the SimpleSession object through msgContext.getSession().
However, for J2EE apps that rely on javax.servlet.http.HttpSession objects, this isn't enough since the SimpleSessionHandler manages it's own Session object list (not to mention there's no easy way to wrap a SimpleSession as an HttpSession.
Assuming that other developers out there need tighter integration between Axis session support and J2EE HttpSession objects, what is the accepted way to do this? Is this a matter of writing a new ServletSessionHandler object to tightly integrate the two types of session objects (along with changes to SimpleAuthenticationHandler and never calling msgContext.getSession())?
Is this work already done and I'm just missing it? Am I running in the wrong direction? Am I using the wrong application design ideals when it comes to working with Axis / web services?
Any pointers would be appreciated... Thanks! justin
____________________________________ Justin Ruthenbeck Software Engineer, NextEngine Inc. justinr - AT - nextengine DOT com Confidential See http://www.nextengine.com/confidentiality.php ____________________________________
