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

["Jochen Kemnade (JIRA)" <ji...@apache.org>]

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

Jochen Kemnade updated TAP5-633:
--------------------------------

    Labels: bulk-close-candidate  (was: tapestry5-review-for-closing)

This issue has been last updated about 1.5 years ago, has no assignee, affects an old version of Tapestry that is not actively developed anymore, and is therefore prone to be bulk-closed in the near future.

If the issue still persists with the most recent development preview of Tapestry (5.4-beta-6, which is available from Maven Central), please update it as soon as possible. In the case of a feature request, please discuss it with the Tapestry developer community on the dev@tapestry.apache.org mailing list first.


> 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
>            Priority: Minor
>              Labels: bulk-close-candidate
>
> 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)