Em Tue, 10 Mar 2009 19:05:21 -0300, Alex Kotchnev <[email protected]>
escreveu:
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).
That's exactly what I'm doing now (URL rewriting support in Tapestry). I'm
planning to do the URL internationalization on the top of it. This would
be done without changing any existing Tapestry code
(ComponentClassResolver, etc). In other words, Tapestry, besides the URL
rewriting code, does not even know that the URLs are being localized, it
just sees the 'developer' URLs.
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
