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 2008/10/31 17:45:44 UTC
[jira] Closed: (TAP5-173) Provide support for subclassing core
components
[ https://issues.apache.org/jira/browse/TAP5-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-173.
-------------------------------------
Resolution: Won't Fix
I'm afraid this is too vague to be fully actionable. It would be useful in terms of specific components, and specific properties/parameters.
> Provide support for subclassing core components
> ------------------------------------------------
>
> Key: TAP5-173
> URL: https://issues.apache.org/jira/browse/TAP5-173
> Project: Tapestry 5
> Issue Type: Improvement
> Affects Versions: 5.0.15
> Reporter: Thiago H. de Paula Figueiredo
> Priority: Minor
>
> Almost all core Tapestry 5 components have all methods with package visibility, something that prevents subclassing them to build new functionality over already existing ones or to change some specify behaviour.
> Other related problem is access to parameters in subclasses, as they need to be private and the core components don't provide getters.
> The only solution found by me and other people in the Tapestry mailing list is to copy the original component code and then apply the needed changes.
> There is a discussion about this at http://www.nabble.com/-T5--About-core-components-subclassing-and-methods-with-package-visibility-to18104118.html.
--
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