Hi Samisa,
It worked for us with very well with Axis2 1.2 The only thing is you need to care is the timeout found in axis2.xml. Best you raise it from 30000 ms to something greater than what your normal longest lasting sessions will take. We adjusted ours to 12 hours. Saying that a user can start a session in the morning and if no other network failure happens during the day, his session will remain established, and will talk to the same instance of his object even after 11h 59min and 59 seconds. But if he sends the sends the second request 4 hours after the first the next timeout will be 12 hours later again. However - now we just migrate to OpenVMS Itanium and Axis2/Java 1.5.1 and we have not yet tested this again. I hope it works the same as it did with axis2 1.2 Sepp Von: Samisa Abeysinghe [mailto:[email protected]] Gesendet: Mittwoch, 14. April 2010 17:34 An: Apache AXIS C User List Betreff: Re: managed session On Wed, Apr 14, 2010 at 1:34 PM, Stadelmann Josef <[email protected]> wrote: Are you talking about scope=soapsession to be included into service.xml. for AXIS2-1.2 this was working for sure. Right, that should work! Samisa... -- blog: http://samisa-abeysinghe.blogspot.com/
