You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Jason Lotz <ja...@gmail.com> on 2009/06/14 03:16:32 UTC

Hooks for code on every page request

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 this logic in the layout
component as it is called on each page request.  However, as this is my
first Tapestry project, I'd like to do things the right way as much as
possible.

If there is a more standard way of doing this, please let me know.  I am
using Tapestry 5.1.

Thanks in advance,
Jason

Re: Hooks for code on every page request

Posted by Olle Hallin <ol...@gmail.com>.
...or just the sample timing filter that the quickstart archetype creates!

Olle


2009/6/15 Thiago H. de Paula Figueiredo <th...@gmail.com>

> On Mon, Jun 15, 2009 at 11:06 AM, Jason Lotz<ja...@gmail.com> 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
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>


-- 
Olle Hallin
Senior Java Developer and Architect
olle.hallin@crisp.se
www.crisp.se

Re: Hooks for code on every page request

Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
On Mon, Jun 15, 2009 at 11:06 AM, Jason Lotz<ja...@gmail.com> 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

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


Re: Hooks for code on every page request

Posted by Jason Lotz <ja...@gmail.com>.
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 <
thiagohp@gmail.com> wrote:

> Em Sun, 14 Jun 2009 02:12:34 -0300, Angelo Chen <
> angelochen960@yahoo.com.hk> 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 as a request filter.
>
> --
> Thiago H. de Paula Figueiredo
> Independent Java consultant, developer, and instructor
> http://www.arsmachina.com.br/thiago
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>

Re: Hooks for code on every page request

Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
Em Sun, 14 Jun 2009 02:12:34 -0300, Angelo Chen  
<an...@yahoo.com.hk> 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 as a request filter.

-- 
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago

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


Re: Hooks for code on every page request

Posted by Angelo Chen <an...@yahoo.com.hk>.
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 this logic in the layout
> component as it is called on each page request.  However, as this is my
> first Tapestry project, I'd like to do things the right way as much as
> possible.
> 
> If there is a more standard way of doing this, please let me know.  I am
> using Tapestry 5.1.
> 
> Thanks in advance,
> Jason
> 
> 

-- 
View this message in context: http://www.nabble.com/Hooks-for-code-on-every-page-request-tp24017828p24018629.html
Sent from the Tapestry - User mailing list archive at Nabble.com.


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