On Sun, 04 Dec 2011 15:05:44 -0200, Kalle Korhonen
<kalle.o.korho...@gmail.com> wrote:
Since URLrewriter is a separate service, couldn't you just lift the
code from 5.2 and put it in your application so you can go on with
your business?
I guess this should work. The old URL rewriter was an ordinary
RequestFilter (URLRewriterRequestFilter) contributed before:StaticFiles
(for incoming URLs) and one advice, ComponentEventLinkEncoderMethodAdvice,
for ComponentEventLinkEncoder (for outgoing URLs).
Just asking - I don't know if there were some drastic
internal changes that would make it impossible to implement
URLrewriter in 5.3.
It was implemented without any internal changes, so it can be easily
turned into a separate package.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
