Hi all,
> > > As I have seen I can choose between three options for session > management > > > Transport, SOAP, and ClientID. Unfortunately I don't know how to > > > configure and handle them. Also I'm not sure about the implied > > > advantages and disadvantages of these options. I would be really > happy > > > if you could shed some light on this. Thanks a lot! > > > > > Have you tried the sample > > http://wso2.org/project/esb/java/1.6/docs/ESB_Samples.html#Sample54 > > Chathura should be able to help you on this further.. > Thanks for that pointer. I wasn't aware of this example. As my own > configuration didn't work out, I'll check this example and compare it > with my tests. After that I'll get back to you. Examples are always of > great value. I promised to get back to you and in fact I do. ;-) The example worked like a shame and I know understand how to solve my problem using one of the above options for sticky session support, namely the ClientID approach. As the name implies the client decides when to create a new "session". Maybe the name ClientSessionID would describe the usage more accurately. Therefore one had just to include the XML-Element "ClientID" from the Synapse-Namespace to the SOAP-Header, which then will get evaluated by the WSO2 ESB to keep the session sticky. So this works great for the use case I have in mind. Just for the sake of completeness I would like to understand the other two options (SOAP and Transport) as well. Could some please elaborate on this! Sorry, if I might have missed some documentation about this. Regards, Eric _______________________________________________ Esb-java-user mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
