Hi Adam, perthread-services are recreated on each request...
> PERTHREAD > An alternate scope provided with Tapestry; a per-thread instance is created > on demand, behind a shared proxy. You could create a simple Object to hold your proxy instead and store it in the session. Something like that: > @SessionState private SFSBWrappingObject yourService; http://tapestry.apache.org/tapestry5.1/guide/appstate.html http://tapestry.apache.org/tapestry5.1/apidocs/org/apache/tapestry5/annotations/SessionState.html http://tapestry.apache.org/tapestry5.1/apidocs/org/apache/tapestry5/services/ApplicationStateManager.html If it's an option to have your Tapestry-App and the OpenEJB backend merged you could try out Tapestry Jumpstart's approach of integrating OpenEJB with Tapestry: http://jumpstart.doublenegative.com.au/ It's quite unfortunate architecture to have stateful services on a remote machine... aren't there any alternatives speaking of architecture? Best, Christian Am 05.11.2010 um 12:56 schrieb Adam Zimowski: > Hi Christian - > > I did not know about @Scope annotation and it is nice. To answer your > question yes, we need to retain a specific sfsb proxy instance per > session, so yes, across multiple requests. Can I annotate service > builder method with @Scope to tell Tap IOC to pull a specific instance > for a session? Or is it purely a global singleton override to merely > return a new instance for each @Inject ? > > To put it differently I would expect Tap IOC to be aware of user > sessions, store sfsb for each session in some sort of a map and on > each @Inject/@InjectService look up the map, if there pull the > instance otherwise create new one. > > Adam > > On Fri, Nov 5, 2010 at 5:51 AM, Thiago H. de Paula Figueiredo > <thiag...@gmail.com> wrote: >> On Fri, 05 Nov 2010 08:30:52 -0200, adasal <adam.salt...@gmail.com> wrote: >> >>> Hi Christian, >> >> Hi, guys! >> >>> You know Tapestry very well. >>> Do you have any points of comparison with JEE JSF, e.g. Ice Faces? >>> It seems to me that JSF is very similar (by borrowed design) to Tapestry. >>> But there must be technical points of significant difference? >> >> I know very little about JSF, but Tapestry 5 is very, very different from >> JSF. The similarity is that their built on Java and are component >> (event)-oriented frameworks. >> >> * Tapestry 5 doesn't use XML configuration besides web.xml, JSF does. >> * JSF has a very complicated lifecycle, Tapestry doesn't. >> * Tapestry is built and configured on an IoC framework, JSF doesn't, so you >> can adapt it to your needs way simpler than JSF. >> * Writing components in Tapestry is way easier. >> * Tapestry has live class reloading, JSF doesn't. >> * In Tapestry, pages are objects in a very OOP sense, while JSF, IMHO, >> doesn't have a page concept. In Tapestry, there's a 1:1:1 relationship >> between the page class, its template and its URL. >> * Tapestry has its own template engine, not using JSP. JSF uses JSP (which >> sucks) or Facelets (which its own documentation says that it was inspired >> from Tapestry's template engine). >> * Tapestry doesn't store page rendering information anywhere, JSF does. >> * Tapestry 5 has native AJAX support. As far as I know, JSF doesn't have. >> * JSF is an specification with two implementations which aren't 100% >> compatible with each other. Tapestry is a framework. >> >> I could go on and on . . . >> >> -- >> Thiago H. de Paula Figueiredo >> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and >> instructor >> Owner, Ars Machina Tecnologia da Informação Ltda. >> http://www.arsmachina.com.br >> >> --------------------------------------------------------------------- >> 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 > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
