> But before doing something unnecessary: I would need a separate instance of > my service for each user session, holding information for this particular > session. Would I get this when switching to the T5.2 IoC?
I haven't heard of anyone implementing a per-session service scope. In T5 instead of having multiple instances of your service per-session you'll either have a singleton or per-thread service with your session state bean stored via the ApplicationStateManager. Josh On Tue, May 31, 2011 at 2:42 PM, Erik Fäßler <erik.faess...@uni-jena.de> wrote: > Hey, thanks for your answer! >>> . >> >> How is this second class getting the service object? If the service is >> singleton (this is the default scope in Tapestry-IoC), the same service >> instance is injected. Don't forget that both classes need to be Tapestry-IoC >> services for them to have service injection. >> > Hm, my application uses Chinellekit to employ Hivemind with Tapestry > 5.2...this is because of legacy reasons. My services are currently defined in > a hivemodule.xml, pooled and set- or constructor-injected. But my plan is to > switch all my services to the Tapestry IoC container anyway. So perhaps I > should just do this first and then see how the thing behaves. > > But before doing something unnecessary: I would need a separate instance of > my service for each user session, holding information for this particular > session. Would I get this when switching to the T5.2 IoC? > > Sorry for my newbie-answers, I'm not yet aware of the full changes of > Tapestry since T4. But working on it...;-) > > Best, > > Erik > --------------------------------------------------------------------- > 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
