The real issue with this kind of annotation-based mapping is that to
accomplish it would require loading all the page classes in the entire
application at startup (or on class reload), just so the annotations
can be read. I may look into another option, reading the annotation
without loading the class into memory. It's still something I've been
trying to avoid due to the overhead. I want Tapestry to scale to
thousands of pages.
On 6/26/07, kranga <[EMAIL PROTECTED]> wrote:
Hi Tapestry developers:
Is it possible to add friendly/custom URL support using annotations? If
I mark my page class with an annotation such as @URL("/a/b/c/foo"), then
Tapestry can internally automatically generate a filter that maps the URL to
my page class. So a request such as /a/b/c/foo?id=1 can be handled by the
appropriate class (in this case setting a field called id to 1). Is this
possible?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
