Thank you for the replys.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3897732#3897732
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3897732
---
This SF.Net email
Jason is right, a load balancer that supports sicky sessions will do. Tomcat
handles the cookies.
Ideally you would pass the buisiness session id in a SOAP header and have a
handler deal with it.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3897655#3897655
The goal to keep J2EE web services stateless is to bring simplicity and aid
interoperability. Given this, I think you are doing the right approach of
passing some form of session identifier to your business method in SLSB.
It is now upto your business code to deal with stickiness. Maybe a com
Is it possible to affect the HTTP header from a statless session
bean that is exposed as a webservice?
Where is it possible to do "header insertion"?
Thanks!
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3897370#3897370
Reply to the post :
http://www.jb
It depends on where you are storing the state. If the state is shared you don't
need stickiness. Otherwise, yes you could use a smart lb and sticky sessions.
Most likely using header insertion.
-Jason
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3897297#389
