You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2010/07/03 00:57:53 UTC
[jira] Assigned: (TAP5-1198) A user defined activate event handler
appears to execute *before* the event handler supplied by
@PageActivationContext, making defensive coding impossible
[ https://issues.apache.org/jira/browse/TAP5-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1198:
------------------------------------------
Assignee: Howard M. Lewis Ship
> 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
>
> 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.