Hmm... what version of tapestry are you using. I created a little test
for 5.0.11 and it looks right to me (although the Object[] came at the
end I'm not sure where that one is supposed to fit in).
http://localhost:8080/start/test/this/args
@OnEvent("activate")
public void alpha()
On further experimentation I find that the onActivate methods are selected
by reverse alphabetical order and by decreasing number of parameters.
Multiple Parameters in onActivateMultiple Parameters in onActivateShall I
reopen https://issues.apache.org/jira/browse/TAPESTRY-1730 ?
Szemere
On Mon
Hi,
onActivate(Object[]) is always called first because it counts as a
method having an infinite amount of parameters, so to speak. At least
that's the way I see it.
-Filip
On 2008-04-14 20:40, Szemere Szemere wrote:
I've been playing around with onActivate methods recently, that is with
mu
I've been playing around with onActivate methods recently, that is with
multiple parameters and multiple methods. I don't understand its behaviour
- it does not seem to match up with the lore on the mailing lists (apologies
for the lack of references). I was wondering if anyone has recent experien
