Well, if you page name is, say, "admin/Menu" then you put your template in WEB-INF/admin/Menu. You class name will be ...pages.admin.Menu.
Allowing templates in WEB-INF adds a touch of ambiguity (the template can go in two places) but its a big convienience, especially for non-Java coders who don't want to have to mess around too deep in the source hierarchy. On 2/22/07, Robert Zeigler <[EMAIL PROTECTED]> wrote:
<snip> On Feb 22, 2007, at 2/2210:57 AM , Howard Lewis Ship wrote: > Tapestry 5 is pretty strict on its name: "catalog" in a URL is a > logical page name. This will be mapped to a particular class: > com.wonderfulhost.my.app.pages.Catalog perhaps. The case of the word > "catalog" doesn't matter. The Catalog page will have a template named > "Catalog.html" and that goes in one of only two places: on the class > path with Catalog.class, or in WEB-INF (the latter case only applies > to application pages, not pages from a library). </snip> So, for templates in WEB-INF, the templates have to reside in WEB-INF proper, or can they reside in some subdirectory of WEB-INF (from your description above, I'm assuming the former, but I wanted to double check my assumption). Thanks, Robert --------------------------------------------------------------------- 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]
