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
