You need a client side message interceptor, which is implemented by adding a behavior to the binding.
The first incoming message is then intercepted, the messagegroupId header is extracted, and stored as addressing header in a user-session-context-obj. >From then on, with each outgoing message . . . The outgoing message is intercepted, and then addressing-header containing the servicegroupId is added to the soap header. The Axis2 engine, joint with addressing.mar's on each side engaged, is then delivering the message to the very same service-object as long as you do not run in to a timeout. This timeout is adjusted within axis2.xml If you are still interested, send me an e-mail. Josef -----Ursprüngliche Nachricht----- Von: Deepal Jayasinghe [mailto:deep...@gmail.com] Gesendet: Montag, 13. Juni 2011 19:41 An: java-user@axis.apache.org Betreff: Re: Axis2 soapsession Example Hi Mahesh, SOAPSession only works withing Axis2 (not even with Axis1), so you will have hard time trying to get that working with .Net. You probably need to write custom code to handle required SOAP header. However, transport session should work, b'coz in Axis2 transport session works using cookies. As long as .Net client sends the cookies you will be able to stay in the same session. Deepal On Thu, Jun 9, 2011 at 2:30 PM, Mahesh kumar <mmahesh...@gmail.com> wrote: > Hi, > I'm new to axis2 webservice. Can anyone provide me example for soapsession. > A .net application is going to consume my service. In this case which > session type is appropriate. Transport session or soap session. Sorry for my > ignorance -- http://blogs.deepal.org --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org For additional commands, e-mail: java-user-h...@axis.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@axis.apache.org For additional commands, e-mail: java-user-h...@axis.apache.org
