Yes it does, if the onActivate() methods are in different places.
There's a very explicit order, base classes handle events before
subclasses. Within a class, its handled alphabetically (ascending)
and by parameter count (descending, for a single method name with
multiple overrides).
What you
Howard,
I'm on 5.0.6. I'll try to boil this down to a simple test case and file
a JIRA. It might have something to do with the page inheritance I'm
using? ThisPage - EditBasePage - BasePage. The onActivate() and
onActivate(Integer) methods are on ThisPage. Would this make a
difference?
Please add to JIRA.
On Nov 24, 2007 9:09 PM, Andy Huhn [EMAIL PROTECTED] wrote:
Hi Howard,
I am on 5.0.6. The behavior you described here is what I expected to
see (I have onActivate() with one parameter, and onActivate() with 0
parameters, and I expected to see onActivate() with one
Hello,
I'm having a problem with onActivate(). Here are my questions:
1) Why is onActivate() called when a context variable is included in the
URL?
2) Is there a way to prevent onActivate() from being called until AFTER
onActivate(Integer prmPrimaryKey) is called?
Here's my dilemma: I want to
You are using 5.0.5? I believe 5.0.6 has a fix for this, wherein the
method invocation order is by number of parameters, decreasing.
You may have to do:
Object onActivate(Object[] context)
{
...
}
And check the context count explicitly, and convert the context values
explicitly, if you are on
Hi Howard,
I am on 5.0.6. The behavior you described here is what I expected to
see (I have onActivate() with one parameter, and onActivate() with 0
parameters, and I expected to see onActivate() with one parameter
executed first...but that was not the case).
Should I file a JIRA? It sounds
