> Mr. Wulf (shit this sounds cool!) :) Well, the available T5 session scopes are singleton and per-thread. Singleton means that the service will be built only once and then shared for all threads and therefore requests. Per-thread means that the service will be built for every single request.
More details here under "Defining Service Scope": http://tapestry.apache.org/defining-tapestry-ioc-services.html Kind Regards, Wulf -----Original Message----- From: esper [mailto:marin_ma...@yahoo.com] Sent: Freitag, 12. Oktober 2012 13:55 To: users@tapestry.apache.org Subject: RE: Tapestry & hibernate session - without tapestry-hibernate module Mr. Wulf (shit this sounds cool!) i didn't even know this could be done! but there is a questions that comes to mind: can injected objects be built on demand (runtime) or is it only once per application session? once per thread basically. you see, there is a reason why I decided to remove tapestry-hibernate module and the reason is I want to rebuild my session on demand. sorry for not trying out your answer, Lance. I will eventually end up there but as for now, with the limited knowledge I have, it's still too much to swallow. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-hibernate-session-without-tapestry-hibernate-module-tp5716838p5716844.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- 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
