On Tue, 29 Mar 2011 19:36:18 -0300, Howard Lewis Ship <hls...@gmail.com>
wrote:
I hope I didn't come off as dismissive ... but I am curious about how
other people approach these problems and whether they take in the big
picture.
I haven't thought much on different implementations for the same feature,
but the first thing I would think is URL rewriting (using LinkTransformer
or something else). Maybe this, in combination with a
ComponentClassTransformer (so the changes in the page class annotations
could be picked at runtime and maybe even avoid the class scanning
completely) could be used to provide an alternative implementation to
tapestry-routing. Alejandro, am I right? :)
--
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
