You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2010/09/18 01:59:32 UTC

[jira] Assigned: (TAP5-1011) When using @PageActivationContext and providing a no-args activate event handler, the handler may be called too soon

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

Howard M. Lewis Ship reassigned TAP5-1011:
------------------------------------------

    Assignee: Howard M. Lewis Ship

> When using @PageActivationContext and providing a no-args activate event handler, the handler may be called too soon
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: TAP5-1011
>                 URL: https://issues.apache.org/jira/browse/TAP5-1011
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>
> It appears that the onActivate() method is called before the @PageActivationContext logic, which means the following can fail:
> @PageActivationContext
> private MyEntity entity;
> void onActivate()
> {
>   if (entity == null) throw new RuntimeException("Entity not found.");
> }
> The RuntimeException is thrown even when a valid Entity is in the page activation context.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.