Hello,
With 5.13 and 5.14, I have a strange behavior when I add an onActivate
method in a super class. The methods are not called in the same order
in my child class.
public class ParentPage {
}
public class ChildPage extends ParentPage {
public void onActivate(Entity e) {
System.out.print("Hello ");
}
public void onActivate() {
System.out.print("World ");
}
}
Like this, I get "Hello World".
Now, if I had a onActivate() method to my ParentPage, I get "World
Hello". Tapestry doesn't call the methods in the same order.
Is it a bug or did I misunderstand documentation ?
Thanks,
Denis
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]