I think that is the approach I will go for but I need to get around a serious stumbling block.
Hivemind Registry is set up in ApplicationServlet..... So if I try to access it in a servlet filter, it may not be created yet. Henrik "Ron Piterman" <[EMAIL PROTECTED]> skrev i en meddelelse news:[EMAIL PROTECTED] > What about creating a hivemind service with the threaded model, which will > hold your thread-state-values? > > öéèåè hv @ Fashion Content: >> Or perhaps I can somehow extend Infrastructure to hold these attributes >> as well for the duration of the request. >> >> "hv @ Fashion Content" <[EMAIL PROTECTED]> skrev i en meddelelse >> news:[EMAIL PROTECTED] >> >>>In my tapestry 3 application I have a servlet filter and an engine >>>service that are attach three objects to the request as Servlet Request >>>attributes. As I understand it I could have an ASO on which I set these >>>three as properties, but I would need a scope of only the request. >>> >>>How would I do this. Just create the ASO with some special scope define. >>>Or also create a service for retrieving the ASO ? >>> >>>Henrik >>> >>> >>> >>>--------------------------------------------------------------------- >>>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] >> >> > > > --------------------------------------------------------------------- > 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]
