[
https://issues.apache.org/jira/browse/TAP5-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884879#action_12884879
]
Hudson commented on TAP5-1198:
------------------------------
Integrated in tapestry-5.2-freestyle #149 (See
[http://hudson.zones.apache.org/hudson/job/tapestry-5.2-freestyle/149/])
TAP5-1198: A user defined activate event handler appears to execute
*before* the event handler supplied by @PageActivationContext, making defensive
coding impossible
> A user defined activate event handler appears to execute *before* the event
> handler supplied by @PageActivationContext, making defensive coding impossible
> ----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1198
> URL: https://issues.apache.org/jira/browse/TAP5-1198
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
> Assignee: Howard M. Lewis Ship
> Fix For: 5.2.0
>
>
> A common technique is to provide a no-argumentes activate event handler
> method that can check to see if the PAC is null, and return a page (or other
> redirect causing result). However, since the @PageActivationContext-related
> event handler executes too late, the field will always be null when that
> method executes.
> Workaround: Don't use @PageActivationContext
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
