It _shouldn't_ change anything, but I'm wondering why Joel is seeing different behaviour, and trying to find out if there is a problem.
I studied this problem a few months ago, looked at the source code (and the Javassist generated source code) and I'm not happy with the current implementation or Howard's proposed solution unless there's more control over multiple event method calls. Short-circuiting for example. And I read Howard's blog. My comment on that post is right before yours. Although your comment was on topic, you might want to read this: http://tapestryjava.blogspot.com/2005/10/blogs-arent-for-support.html Cheers, Nick. Marcus-11 wrote: > > NIck, > > "When a single method is overloaded with different parameters, the order > of > invocation is fewest parameters to most parameters." commented by Howard > at > (https://www.blogger.com/comment.g?blogID=4110180&postID=7231241573208214842 > ) > > So, reversing the order of methods don't should change anything. > > Anyway, T5 should call only those methods that matches, and onActivate(), > with no parameters, first. > > Marcus > > -- View this message in context: http://www.nabble.com/T5%3A-Activation-contexts-tf4356640.html#a12445691 Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
