You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2014/08/28 02:56:59 UTC

[jira] [Closed] (TAP5-633) Allow page classes to have a "Page" suffix that is not included in the URL

     [ https://issues.apache.org/jira/browse/TAP5-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-633.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.4
         Assignee: Howard M. Lewis Ship

> Allow page classes to have a "Page" suffix that is not included in the URL
> --------------------------------------------------------------------------
>
>                 Key: TAP5-633
>                 URL: https://issues.apache.org/jira/browse/TAP5-633
>             Project: Tapestry 5
>          Issue Type: Improvement
>          Components: tapestry-core
>    Affects Versions: 5.1.0.2
>            Reporter: Paul Field
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>              Labels: bulk-close-candidate
>             Fix For: 5.4
>
>
> I have an application with a lot of read-only pages. For example, I have a page that shows a company and I would like a URI such as:  /company/1234
> However, if I name the page class "Company" then I get a naming clash with the domain object "Company". What I would like to do is call the Tapestry 5 class "CompanyPage" - after all, that is what the class represents and it's certainly how the team refers to that thing internally and with our business (i.e. "Have you seen the new company page?").
> So, please could the ComponentClassResolverImpl remove the suffix "Page" (if it exists) from the class name when it constructs the logical page name?



--
This message was sent by Atlassian JIRA
(v6.2#6252)