Em Mon, 09 Mar 2009 20:01:33 -0300, Howard Lewis Ship <[email protected]>
escreveu:
I think to handle this you're going to see longer start up times, as
Tapestry will have to load all page classes to look for the
annotations that can drive this. It's something I've been avoiding.
My plans is to accomplish that without scanning all page classes, maybe
just some property files (app.properties and its localized versions).
Tapestry itself (RequestFilters, Dispatchers) wouldn't even know that this
URL i18n is being done. I just don't know yet how I would i18nalize the
link creation, but maybe decorating LinkFactory will do the trick.
I've already finished the initial URL rewriting infrastructure (without
URL i18n). I just need to write the documentation.
--
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]
