You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2009/02/19 23:44:02 UTC
[jira] Updated: (TAP5-216) Many methods of the Page interface could
be moved to PageResources (which should be renamed to
ComponentPageElementResources)
[ https://issues.apache.org/jira/browse/TAP5-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship updated TAP5-216:
--------------------------------------
Issue Type: Improvement (was: Bug)
> Many methods of the Page interface could be moved to PageResources (which should be renamed to ComponentPageElementResources)
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-216
> URL: https://issues.apache.org/jira/browse/TAP5-216
> Project: Tapestry 5
> Issue Type: Improvement
> Affects Versions: 5.1.0.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Priority: Minor
> Fix For: 5.1.0.0
>
>
> Just an observation; many methods on Page were done to cut down on the number of injections passed to each ComponentPageElementImpl ... however, since then the PageResources interface was introduced to act as a facade over services needed by the ComponenPageElementImpl.
> I think several methods of Page could be moved to PageResources, which would simplify PageImpl and the (increasing number of) dependencies passed to it.
> Also, PageResourcs could be renamed ComponentPageElementResources, and a new PageResources facaded could be introduced for PageImpl.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.