tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Markus Wiederkehr <markus.wiederk...@gmail.com>
Subject Re: DataSqueezers in Tapestry 4.0
Date Fri, 05 Aug 2005 10:44:16 GMT
On 8/5/05, Norbert Sándor <developer@erinors.com> wrote:
> As I see it is not accessible. Maybe put the IRequestCycle to a ThreadLocal
> so you can access it from anywhere.

It actually seems to work!

I have overridden AbstractEngine.createRequestCycle() to set the
request cycle to a ThreadLocal. And I have added a static
lookup-method to my Engine to retrieve the request cycle that belongs
to the current thread. I believe that is what you had in mind,

I hope (and believe) that it's safe to assume that
AbstractEngine.createRequestCycle() will always be invoked before any
data squeezers get invoked.

Thanks a lot,


To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org

View raw message