this where my considerations:
- i have a listener with useful parameter names/types
- i do not have to define any abstract properties thus keeping
my controller class simpler and cleaner (.. and less code in .page :))
i will try as you propose :)
but what bothers me is that i have a validator applied to the TextField.
Shouldn't Tapestry check the validators before it proceeds to execute
the listeners?
I'm must admit, i'm not aware at which point of the request processing
lifecycle validation is done. i was alw
hi jesse,
this bug is filed as
https://issues.apache.org/jira/browse/TAPESTRY-1240
greetings
kris
"Jesse Kuhnert"
<[EMAIL PROTECTED]