Is there any way to maintain session information within AXIS?
When an AXIS client issues a call, the marshaller wraps the HTTP header around the SOAP message so
the client has no way of accessing the HTTP session information. Similarly, the server code only has
access to the SOAP stuff, not the HTTP requests. Is there a way to overcome this?

Reply via email to