Advantages to Declaring Pages in .app file?

Is there an advantage to Tapestry's requirement that pages be declared in 
the .application file, or is this a simply a side-effect of storing pages 
in the classpath?

I ask because I wanted to contribute to the Wiki discussion of  _The 
Location of Templates_, but realized that I wasn't sure if the declarative 
page model was one of the original goals of Tapestry.  What I would like to 
propose is that .page's and templates be kept in a directory named:

WEB-INF/[appName]/pages

But I realized that once pages and templates are located in one place, they 
become easy for Tapestry to find and index - thus minimizing the need to 
declare them in the .application file.  Pages *could* still be declared in 
the .app file, but the meaning would become similar to declaring an alias 
for the page.

Carrying this a bit further, the search order for .page's and templates 
could be /pages first, then classpath.  This would also allow neat tricks 
like easily replacing templates bundled in jars simply by placing a new 
template in a matching folder structure of the /pages directory.

Any thoughts?  If there is not strong objection, I will post it to the 
Wiki.  I really was just wondering if people would scream if I suggested 
minimizing the importance of declaring pages in the .app file.

Thanks,

Eric Everman



-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing 
your web site with SSL, click here to get a FREE TRIAL of a Thawte 
Server Certificate: http://www.gothawte.com/rd524.html