Em Mon, 30 Mar 2009 18:21:14 -0300, xfile80303 <l...@grokers.net> escreveu:
Hi Thiago, all,
Hi!
Thanks for adding this feature.
:)
Is there a way to utilize this to only rewrite page render requests and not component or asset requests? I know it is pretty early on in the request lifespan, but without this discrimination this feature is not nearly as useful to me (and possibly others?).
It's really very early in the request handling pipeline. Maybe Tapestry should add some way (maybe methods in the Request instance) that tells if the given request is an page one or an event one or an asset one or etc.
Don't forget that every rules can choose if it will overwrite the request (returning another Request instance) or not, so your rule must first check if the request is one that needs to be rewritten or not. What exactly is the URL rewriting you want to do?
-- Thiago H. de Paula Figueiredo Independent Java consultant, developer, and instructor http://www.arsmachina.com.br/thiago --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
