According to the documentation I have read session management is supported in JAX-RPC and the Axis documentation seems to indicate it supports sessions. See the following:
http://ws.apache.org/axis/java/user-guide.html Support for session-oriented services, via HTTP cookies or transport-independent SOAP headers http://java.sun.com/xml/jaxrpc/overview.html JAX-RPC supports HTTP level session management and SSL based security mechanisms. This enables you to develop secure Web services. More advanced SOAP message-level security will be addressed in the evolution of JAX-RPC technology. http://java.boot.by/wsd-guide/ch04s04.html Given a set of requirements, develop and configure a Web service client that accesses a stateful Web service. The JAX-RPC specification requires that a service client be able to participate in a session with a service endpoint. In the JAX-RPC 1.1 version, the session management mechanisms require use of HTTP as the transport in the protocol binding. This version of the JAX-RPC specification does not specify (or require) session management using SOAP headers given that there is no standard SOAP header representation for the session information. SOAP based session management may be considered in the future versions of the JAX-RPC specification. A JAX-RPC runtime system is required to use at least one of the following mechanisms to manage sessions: * Cookie based mechanism: On the initial method invocation on a service endpoint, the server side JAX-RPC runtime system sends a cookie to the service client to initiate a new session. If service client wants to participate in this session, the client side JAX-RPC runtime system then sends the cookie for each subsequent method invocation on this service endpoint. The cookie associates subsequent method invocations from the service client with the same session. * URL rewriting involves adding session related identifier to a URL. This rewritten URL is used by the server-side JAX-RPC runtime to associate RPC invocations to the service endpoint with a session. The URL that is rewritten depends on the protocol binding in use. * SSL session may be used to associate multiple RPC invocations on a service endpoint as part of a single session. A session (in JAX-RPC) is initiated by the server-side JAX-RPC runtime system. The server-side JAX-RPC runtime system may use javax.servlet.http.HttpSession (defined in the Servlet specification) to implement support for the HTTP session management. A service client uses the javax.xml.rpc.session.maintain property (set using the Stub or Call interfaces) to indicate whether or not it wants to participate in a session with a service endpoint. By default, this property is False, so the client does not participate in a session by default. However, by setting javax.xml.rpc.session.maintain property to True, the client indicates that it wants to join the session initiated by the server. In the cookie case, the client runtime system accepts the cookie and returns the session tracking information to the server, thereby joining the session. The client code by setting the javax.xml.rpc.session.maintain property assumes that it would participate in a session if one is initiated by the server. The actual session management happens transparent to the client code in the client-side runtime system. -----Original Message----- From: Rajdeep Dua [mailto:[EMAIL PROTECTED] Sent: Thursday, February 24, 2005 4:04 AM To: [email protected] Subject: Re: Session management Web service impl using JAX-RPC is supposed to be stateless.that could be the reason. --- JR Ruggentaler <[EMAIL PROTECTED]> wrote: > I have a functioning Axis web service that's called > by a third party tool (bevocal.com). I set > messageContext.setMaintainSession(true) but > messageContext.getMaintainSession() always returns > false. A new session is created for each call. What > do I need to do to maintain sessions between Axis > and a non Axis client? I am testing with > org.apache.axis.transport.http.SimpleAxisServer, > does SimpleAxisServer affect session Management? My > deploy.xml contains: <parameter name="scope" > value="session"/> > > Thanks in advance! > J.R. > __________________________________ Do you Yahoo!? Yahoo! Mail - now with 250MB free storage. Learn more. http://info.mail.yahoo.com/mail_250
