[TAPESTRY-109] cycle.activate() does not throw an exception when called at an inappropriate time

• Type: Bug
• Status: Resolved
• Resolution: Won't Fix
• Affects Version/s: 2.3
• Component/s: Framework
• Environment: Operating System: Other; Platform: PC
• Bugzilla Id: 26387
• Assignee: Unassigned
• Reporter: Christopher Corde
• Created: 24/Jan/04 05:52
• Updated: 10/Mar/06 10:00
• Resolved: 10/Mar/06 10:00

Description

When calling cycle.activate() from within the pageBeginRender() method or
pageValidate() method, Tapestry takes no action to activate the page. This is
correct behavior, because activate() should not be called, however an exception
should be thrown and propagated up to notify the developer.