[TAP5-1198] A user defined activate event handler appears to execute *before* the event handler supplied by @PageActivationContext, making defensive coding impossible

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.2.0
• Fix Version/s: 5.2.0
• Component/s: tapestry-core
• Assignee: Howard Lewis Ship
• Reporter: Howard Lewis Ship
• Created: 02/Jul/10 22:55
• Updated: 03/Jul/10 00:53
• Resolved: 02/Jul/10 23:33

Description

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