Peter -- One quick thought -- the .wsdd mentions 'pivot' and I remember reading in the Axis documentation about their notion of a pivot point in the communication pipeline. As I remember, a pivot point is where a message changes from being a response to being a request. You might check out the Axis Architecture Guide (http://ws.apache.org/axis/java/architecture-guide.html) and see if anything in there addresses your question more specifically. It looked pretty general, but it might point you in the right direction.
Hope this helps! -mike somerville. -----Original Message----- From: Peter Molettiere [mailto:[EMAIL PROTECTED] Sent: Monday, July 26, 2004 8:39 PM To: [EMAIL PROTECTED] Subject: HttpClient and Tomcat: Can someone explain something? I'm wondering if someone can explain something fairly basic for me. We're using axis with CommonsHTTPSender in order to get Keep Alive to work, in preparation for implementing SSL. I understand how the axis config can control the class which does the socket handling on the client, but on the server, it seems that Tomcat would be handling the HTTP connection itself, and just handing AxisServlet the HTTPServletRequest and Response objects -- ie., I don't see how axis gets a chance to configure what class does the HTTP connection handling in Tomcat. How does this work? Does Tomcat actually use HTTPClient when you specify the following in deploy.wsdd? <transport name="http" pivot="java:org.apache.axis.transport.http.CommonsHTTPSender"> <requestFlow> <handler type="URLMapper"/> <handler type="java:org.apache.axis.handlers.http.HTTPAuthHandler"/> </requestFlow> <parameter name="qs:list" value="org.apache.axis.transport.http.QSListHandler"/> <parameter name="qs:wsdl" value="org.apache.axis.transport.http.QSWSDLHandler"/> <parameter name="qs:method" value="org.apache.axis.transport.http.QSMethodHandler"/> </transport> How does that work? Where should I start looking to understand this piece of axis? Thanks for any help at all. --Peter
