Well, in my case when I have two or more onActivate handlers I've seen all
them called one after the other wich of course is not what I expect ,besides
the fact of having just one onActivate frees you of having to check common
isues like for example loggin , or administrative rights in many places.
-- 
View this message in context: 
http://www.nabble.com/T5-onActivate-tp17673637p17707583.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]

Reply via email to