Aside from the reason I just mentioned, T5 has to know where to look to
find pages (meaning a java package). With your suggested annotation only
half the work is done. If I'm not mistaken there is no clean way to
aggregate all loaded classed in the JVM. If there was, then T5 would
have to scan *all* of them for your annotation. I'd bet a good deal of
money that that would cause a performance hit ;-). Having a known set of
locations to look in solves the performance issue and answers the
generally unimportant question of where pages should live.
Mohammad Shamsi wrote:
i just know that Tapestry use this location for looking up pages.
how about a simple Annotation for page classes instead of ?
just with using a simple Annotation (for exmaple @Page) for a Page Class
we code place classes every where that we like.
On Dec 26, 2007 3:16 PM, Chris Lewis <[EMAIL PROTECTED]> wrote:
Because it removes the necessity to think about something that generally
doesn't deserve thought. If you want them elsewhere, make a contribution
in your app module.
chris
Mohammad Shamsi wrote:
Hi,
i want to know that why i should place my pages and components in
special
folder ?
any idea ?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
