1. It's a very bad idea to have 2 onActivate methods with the same parameter count. If I hit the URL "/yourpage/true/somePage", how does tapestry know which one to call?
2. I have NEVER needed multiple onActivate methods. If I need to handle multiple cases, I have a single onActivate(EventContext) method. 3. If you still want multiple onActivate methods, return true to avoid processing other onActivate methods. -- View this message in context: http://tapestry.1045711.n5.nabble.com/activation-context-method-tp5716091p5716093.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
