I am afraid there is no way around adding some logic to the listener method.
You could delegate the logic of the validation to a service. This might
be cumbersome if you want real friendly validation messages (which
include field label names).
Cheers,
ROn
Christian Mittendorf wrote:
Hello!
Tapestry offers a couple of methods for validating form fields. Version
4 is pretty great
and the new features are really helpful. Congratulations to the new
release!
My question now is focussing on validating complex objects. And I think
that I don't get
the big picture yet. Each of the complex objects propertys is bound to
form fields and each
of these fields has its own validation rules. Custom validators for
each field will do the
job just fine.
But there is one rule that must be applied for the whole object, when
each of the objects
properties has been set. At which point can I execute that rule? Is
there any "established"
best practice, some - in the spirit of Tapestry - fast and easy solution?
I can - of course - use the listener method of the submitted form. That
would be a simple and
easy solution. But I would like to decouple the listener method from
validating these objects.
How would I accomplish that?
Thanks for any hint or recommendation!
Christian
P.S. I hope I was able to explain my "problem".
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
