tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <...@tapestry.apache.org>
Subject [jira] Assigned: (TAPESTRY-1382) Strip out duplication of names in the class name -> page name / component type conversion
Date Thu, 19 Apr 2007 13:14:15 GMT

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

Howard M. Lewis Ship reassigned TAPESTRY-1382:

    Assignee: Howard M. Lewis Ship

> Strip out duplication of names in the class name -> page name / component type conversion
> -----------------------------------------------------------------------------------------
>                 Key: TAPESTRY-1382
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1382
>             Project: Tapestry
>          Issue Type: New Feature
>          Components: tapestry-core
>    Affects Versions: 5.0
>            Reporter: Howard M. Lewis Ship
>         Assigned To: Howard M. Lewis Ship
> When Tapestry converts a class name into a page name, component type or mixin name, it
could be a little smarter: when the package name is either the prefix or the suffix of the
simple class name, it should be stripped off.
> Example: org.example.myapp.pages.book.EditBook --> book/edit (not book/editbook).
 Likewise, org.example.myapp.pages.book.BookIndex --> book/index.
> This does open up a little possibility for name collisions (what if class Index and class
BookIndex are in the book package?).
> The alternative is to have many different classes with the same simple name (List, Edit,
Index, etc.) in different packages, which is much harder to maintain.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org

View raw message