If the work to be done is something not directly affecting pages and components (i.e.: wrapping a request around a UserTransaction), that may be done by a custom javax.servlet.Filter implementation wrapping the Tapestry servlet.
What's the purpose of this code? It could help in finding a better place. Regards, ----------------------------------- Giampaolo Tomassoni - IT Consultant Piazza VIII Aprile 1948, 4 I-53044 Chiusi (SI) - Italy Ph: +39-0578-21100 > -----Messaggio originale----- > Da: butterdave [mailto:[EMAIL PROTECTED] > Inviato: martedì 21 marzo 2006 22.10 > A: [email protected] > Oggetto: An Engine Service that always runs? > > > > Hi, in our previous Tapestry 3 implemenation we overrode the > BaseEngine to do > work whenever we called the following methods: setupForRequest, > cleanupAfterRequest and createRequestCycle. > > Now in Tapestry 4 those methods have been removed. What I'm understanding > now is that I need to write my own service which is configured through > hivemind and then inject that service on whatever page/component > that needs > it. > > However I need this particular work to be done for all requests for all > pages/components. > > Can anybody give some advice? > -- > View this message in context: > http://www.nabble.com/An-Engine-Service-that-always-runs--t1320094 > .html#a3521101 > Sent from the Tapestry - User forum at Nabble.com. > > > --------------------------------------------------------------------- > 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]
