If you have your service in the session it also means that there is the ioc registry attached to it, it could be a problem when you have a cluster, best practices is to store only serializable objects.
Denis Feb 2, 2012 v 9:35 AM, Christian Köberl: > 2012-02-02, John Bush: >> I have a project where I need some services session scoped, not >> singletons or perthread. The reason is that I have some web services >> I use that need some session state for initialization. While the >> perthread approach works just fine, I don't want to be initializing >> that stuff with every request. Calling out to wslds and all the xml >> mumbo jumbo is resource intensive. > > Maybe it would be better to have the web service handling in a singleton > service (and initializes wsld and xml stuff there) which is injected > into the thread scoped - this might work as well. > In Tapestry you can mix service scopes. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
