> A bunch of the next-gen web frameworks ( Rails, Grails, Wicket) have a way
> of specifying some kind of URL rewriting to provide friendly URLs. The whole
> point of having a web framework is to pull the common usage patterns
> together and make them convenient to use. If Tapestry shouldn't reinvent and
> maintain the wheel (that is, URL rewriting), then it should at least provide
> clean integration w/ an existing wheel (as it does w/ its Spring & Hibernate
> integration) that fits well w/ the existing T5 usage patterns (e.g. maybe
> the ability to configure the Tuckey URL rewriting for T5 pages).

Just setting that filter to be run before T5's will do the trick - not
much else should be needed



-- 
Andreas Andreou - [email protected] - http://blog.andyhot.gr
Tapestry / Tacos developer
Open Source / JEE Consulting

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to