...or just the sample timing filter that the quickstart archetype creates!
Olle
2009/6/15 Thiago H. de Paula Figueiredo
> On Mon, Jun 15, 2009 at 11:06 AM, Jason Lotz wrote:
> > Thanks, I think the request filter is what I was looking for.
>
> You're welcome!
> You can use the Tapestry Access
On Mon, Jun 15, 2009 at 11:06 AM, Jason Lotz wrote:
> Thanks, I think the request filter is what I was looking for.
You're welcome!
You can use the Tapestry Access Logger
(http://www.arsmachina.com.br/project/tapestryaccesslogger) for a
request filter example.
--
Thiago
Thanks, I think the request filter is what I was looking for.
Jason
On Sun, Jun 14, 2009 at 11:26 AM, Thiago H. de Paula Figueiredo <
thiag...@gmail.com> wrote:
> Em Sun, 14 Jun 2009 02:12:34 -0300, Angelo Chen <
> angelochen...@yahoo.com.hk> escreveu:
>
> maybe dispatcher? you can find a relat
Em Sun, 14 Jun 2009 02:12:34 -0300, Angelo Chen
escreveu:
maybe dispatcher? you can find a related articles in the wiki page for
t5.
Or a request filter. A dispatcher is more suited for logic that needs page
redirection. For example, I implemented an access logging package
implemented
maybe dispatcher? you can find a related articles in the wiki page for t5.
Jason Lotz wrote:
>
> Are there any standard hooks in the Tapestry framework that I should use
> if
> I want to process some logic on each page request? The quick-and-dirty
> solution for my architecture would be to put
