You can build a Tapestry ioc service around your notification receiver thread which manages the thread and exposes any notification received. This service can then be injected into your pages and components and can be queried for any received notifications.
See http://wiki.apache.org/tapestry/Tapestry5HowToRunTaskInThread and http://wiki.apache.org/tapestry/Tapestry5HowToWorkQueue for examples. HTH, Uli Am Di, 7.10.2008, 09:24, schrieb Edouard sur edouardmercier.fr: > Hi everyone. > > I'm currently facing the following problem: my T5 (0.15) web > application receive notifications in a dedicated non servlet thread > inside some of my Tapestry components, which have an > ApplicationStateObject attribute. I would like to update the state of > the ASO, but the problem is that the thread that triggers some > callback in my Tapestry component cannot thus access the AOS (since I > guess resort to ThreadLocal attributes inside the IoC). I can bind the > dedicated notification thread to the servlet thread that created it. > > Is there a way in Tapestry to work this around, please? > > Thank you. Cheers, Édouard > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
