tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TAP5-1860) problems with protected component fields
Date Thu, 12 Apr 2012 15:37:17 GMT

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

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

The intent is that protected instance fields accessed from a base class are, in fact, instrumented.
 So there's probably a bug here.
                
> problems with protected component fields
> ----------------------------------------
>
>                 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
>         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

        

Mime
View raw message