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 common database in a cluster which stores data that is dependent on state id that was passed to the biz method. As far as the WS infrastructure is concerned, it has dispatched the request that contains custom session id to the bean. Now as a biz developer, deal with it. :-) The possibilities are endless. Keep stateless in mind and you will be happy. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3897520#3897520 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3897520 ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
