On Wed, 28 Jun 2006 11:08:29 -0400, Jesse Kuhnert <[EMAIL PROTECTED]>
wrote:
If you find yourself doing this this way you should still question it,
because now you can do this much more simply:
Your page/component class listener method:
@EventListener(events="onchange", targets="country",
submitForm="myformid")
public void dooFoo(BrowserEvent event)
{
// do whatever you want
}
Just to be clear, you're saying that if I go this way, I don't even need
to provide the onchange handler -- Tapestry will just do it for me? Or,
should my onchange still be doing a submit, but using one of the methods
you listed previously?
Thanks,
Kevin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
