[jira] [Resolved] (TAP5-1311) @ActivationRequestParameter fields in subclass not set prior to "activate" handler in superclass

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

     [ https://issues.apache.org/jira/browse/TAP5-1311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship resolved TAP5-1311.
----------------------------------------

    Resolution: Invalid
      Assignee: Howard M. Lewis Ship

@ActivationRequestParameter operates by adding event handling logic for the "activate" event; however that logic follows the general guidelines of parent class before subclass. That means all activate event logic in the base class is handled first, then activate event logic in the sub class (including @ActivationRequestParameter).


> @ActivationRequestParameter fields in subclass not set prior to "activate" handler in superclass
> ------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1311
>                 URL: https://issues.apache.org/jira/browse/TAP5-1311
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.2.1
>            Reporter: Vjeran Marcinko
>            Assignee: Howard M. Lewis Ship
>
> @ActivationRequestParameter fields in page subclass are not set prior to calling "activate" handler in superclass page. Ordering is proper if activate handler and @ActivationRequestParameter fields are in same page class.
> This bug is present in 5.2.1 and not in 5.2.0.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira