trsvax wrote: > > I know it's documented but is there any real reason the > ActivationRequestParameter annotation only works in a page and not a > component? I realize poor naming conventions could cause conflicts but > it seems like an unnecessary restriction. >
I think that's a very good restriction - I also think that activate/passivate should not be handled/raised by/to components. The first point on our Tapestry best practice list is: Never use onActivate/passivate in components. There are many problems with activation context in components: * One problem is when you reuse the component and are not aware of the activation context handling. * I guess the framework's problem is to handle multiple onPassivates. If you have to components with an activation context to passivate, which one should Tapestry take? -- Chris -- View this message in context: http://tapestry.1045711.n5.nabble.com/ActivationRequestParameter-only-works-in-a-page-tp4932370p4932417.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
