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 (Closed) (JIRA)" <ji...@apache.org> on 2012/04/13 00:21:19 UTC
[jira] [Closed] (TAP5-1860) Access to protected component fields
does not always reflect in subclasses
[ https://issues.apache.org/jira/browse/TAP5-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1860.
--------------------------------------
Resolution: Fixed
Fix Version/s: 5.4
5.3.3
> Access to protected component fields does not always reflect in subclasses
> --------------------------------------------------------------------------
>
> Key: TAP5-1860
> URL: https://issues.apache.org/jira/browse/TAP5-1860
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.3.2
> Reporter: Olaf Tomczak
> Assignee: Howard M. Lewis Ship
> Fix For: 5.3.3, 5.4
>
> Attachments: testapp.tgz
>
>
> There seems to be a problem with the new feature introduced in 5.3.2 - https://issues.apache.org/jira/browse/TAP5-1801
> When I create a protected field in by base page class, setting the field in a subclass' event handling method seems to have no effect.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira