[
https://issues.apache.org/jira/browse/TAPESTRY-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Lewis updated TAPESTRY-1923:
----------------------------------
Attachment: access-to-pages.patch
Here is a simple patch that adds a method to the interface
(ComponentClassResolver#getLogicalPageNames), as well as an implementation to
the internal service. Its a simple implementation (the work was already done)
that follows the concurrency measures taken in other similar methods. What may
be in question is if the naming and return types follow convention as I don't
know what they are.
> ComponentClassResolver can/should provide access to all known page names
> ------------------------------------------------------------------------
>
> Key: TAPESTRY-1923
> URL: https://issues.apache.org/jira/browse/TAPESTRY-1923
> Project: Tapestry
> Issue Type: New Feature
> Components: tapestry-core
> Reporter: Chris Lewis
> Priority: Minor
> Fix For: 5.0.7
>
> Attachments: access-to-pages.patch
>
>
> ComponentClassResolver knows about all pages in the application. It has been
> requested that this be explpoited as a usable feature provided by the
> implementing service, as it may be useful to access such a list.
> This issue is a response to this thread on the mailing list:
> http://www.nabble.com/T5-How-to-get-all-page-names--tf4839337.html#a13848595
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
