You can look at the thread "Axis2 Manage Session Cookie Manually"
On 4/25/07, Paul Fremantle <[EMAIL PROTECTED]> wrote:
Nencho Think of this as a cookie. The client has to be enabled to respond with cookies, but that doesn't create the cookie in the first place. To make this work you need to set <service scope="soapsession"> in services.xml Now the server will set the ref params in the reply-to header. If you have setManageSession(true) now the client will send them back. Paul On 4/25/07, Nencho Lupanov <[EMAIL PROTECTED]> wrote: > Hi All, > > I read this axis2 session management article: > http://www.developer.com/java/web/article.php/3620661 > > Basically, it says that i can define my services being of a soap session > scope, > then i have to put this option on my client: > options.setManageSession(true); > > Therefore it is expected for the service to include > <wsa:ReferenceParameters> > element as an session identifier in the soap envelope. > > I tested this and it does not work - axis2 does not put that element, in > order > to be used as session identifier.Am i missing something or this is a bug? > > Thanks, > Nencho > > -- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://bloglines.com/blog/paulfremantle [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
