That's implemented in Tapestry 4.0.
--
Ing. Leonardo Quijano Vincenzi
DTQ Software
Rusty Phillips wrote:
I don't know if this comes up for you or not, but it does for me.
I occasionally make something (not a Tapestry object, since I'm a newbie
at it) that's got more pages than I'd care to see all at once.
My general approach to dealing with these pages is to keep them in
categories and build a folder-hierarchy to hold my category hierarchy.
Then I can quickly get to whatever type of thing I've got. I noticed
that referring to a page on a path - such as for instance
"localhost:8080/app?page=test/home.html" - fails to find
ROOT/test/home.html
Consider that Tapestry is specifically designed to deal with components.
When you build everything from tiny units, the sheer quantity of tiny
parts tend to add up. I would prefer to organize them. Is there any
way to use anything that's not an immediate child of the context root or
its WEB-INF folder? Has anyone come up with something that already does
that? Is this specifically something that is being avoided, and if so,
why?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
