[jira] [Commented] (TAP5-1860) Access to protected component fields does not always reflect in subclasses

["Howard M. Lewis Ship (Commented) (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TAP5-1860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13252843#comment-13252843 ] 

Howard M. Lewis Ship commented on TAP5-1860:
--------------------------------------------

Already seeing some incorrect bytecode, in the intermediate class, Parent:


      onOther()V
       L0
        LINENUMBER 14 L0
        ALOAD 0
        ICONST_1
        PUTFIELD test/base/pages/other/Parent.fieldSetOnEvent : Z


... thought it might be due to name collision, but nope.  That is, the fact that each class defines a method named "onOther()".  


Awesome. I now have a test case that fails in the Plastic test suite.
                
> 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
>         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