There's two different contexts here: the page's activate context
(produced by the "passivate" event, provided to the "activate" event
and the Form component's context, which is provide to event handler
methods related to the Form ("success", "prepare", etc.).
The Form does not fire an "activate" event; the framework fires the
"activate" event, on the page (not the Form), passing the page's
activation context.
On 6/28/07, Ben Tomasini <[EMAIL PROTECTED]> wrote:
I was using the following code:
Start.html
<t:form context="literal:test">
<t:submit />
</t:form>
Start.java
void onActivate() {
System.out.println("No args");
}
void onActivate(String value) {
System.out.println("String arg");
}
On a form submit, the console shows:
No args
I expected the form tag above to invoke the onActivate method with matching
arguments, it only invokes the noargs method. Is this a bug, by design, or
am I missing something?
Ben
--
Howard M. Lewis Ship
TWD Consulting, Inc.
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Apache HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
