At the moment my conclusion is that to deal with multiple onActivate parameters you should encompass them in an Object[], and then make your control in just one onActivate(Object[] o) method, the drawback is that it forces you to write metods for setting the parameters properties.
Strangelly if you have more than one onActivate they are all called so better to just have one.. -- View this message in context: http://www.nabble.com/T5-onActivate-tp17673637p17695969.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
