[
https://issues.apache.org/jira/browse/TAP5-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252957#comment-13252957
]
Hudson commented on TAP5-1860:
------------------------------
Integrated in tapestry-5.3-freestyle #22 (See
[https://builds.apache.org/job/tapestry-5.3-freestyle/22/])
TAP5-1860: Access to protected component fields does not always reflect in
subclasses (Revision 1325552)
Result = FAILURE
hlship : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1325552
Files :
*
/tapestry/tapestry5/branches/5.3/plastic/src/main/java/org/apache/tapestry5/internal/plastic/FieldInstrumentations.java
*
/tapestry/tapestry5/branches/5.3/plastic/src/main/java/org/apache/tapestry5/internal/plastic/PlasticClassImpl.java
*
/tapestry/tapestry5/branches/5.3/plastic/src/main/java/org/apache/tapestry5/internal/plastic/PlasticClassPool.java
*
/tapestry/tapestry5/branches/5.3/plastic/src/test/groovy/org/apache/tapestry5/plastic/FieldConduitTests.groovy
> 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
