The current rules allow for this: pages.view.ViewArticle is mapped to "view/article" (not "view/viewarticle").
This is very useful, since you'll likely add other options: "add/" or "edit/" or "search/". On 6/12/07, David Peterson <[EMAIL PROTECTED]> wrote:
I'm finding that I often want my pages to have the same names as classes in my model. For example, I have an Article class in my model and I want the article viewer URL to be "/article" (with a context specifying the article reference). Although this is possible by using fully-qualified class names everywhere, it's messy and error prone. Ideally, I'd like to have the URL "/article" mapped to com.mydomain.pages.ArticleViewer. Is that easy to do? (If it's possible could you post some code?) If not, how about a "Page" suffix for page classes, e.g. ArticlePage? I think that would be a useful convention and might avoid having to compromise the URLs, model class names or code readability. David
-- 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]
