1. Validators are designed to cause a single failure each. If you want to
validate multiple things, add multiple validators to a field.
http://tapestry.apache.org/forms-and-validation.html
2. Validators must throw a ValidationException in order to fail, the issue
you are responding to is discussi
at once and
doesn't have to iterate through them and get frustrated.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/T5-ValidationException-from-validate-event-leads-to-ERROR-level-logger-statement-tp4860047p5669953.html
Sent from the Tapestry - User mailing l
or page name as String, without injecting the page
on the component).
Thanks.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/T5-ValidationException-from-validate-event-leads-to-ERROR-level-logger-statement-tp4860047p5654429.html
Sent from the Tapestry - User mailing list
On Tue, 17 Apr 2012 19:31:54 -0300, raulmt wrote:
I know there are alternatives to throwing ValidationExceptions, but I was
wondering what use does this has then? Is there really a case where you
could want to log with error level all the user input validation errors?
I ask because this metho
page as "you should do it this way"
(http://tapestry.apache.org/forms-and-validation.html) but this behavior,
imho, makes it useless at least in most cases.
Regards,
Raul.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/T5-ValidationException-from-validate-even
Thanks to Thiago i found a clean solution:
@Environmental
private ValidationTracker tracker;
Using this envirnmental service one can record validation messages without
throwing exceptions and without having the surrounding form component at hand.
thanks thiago
felix
On 04.10.2011 12:38, Fel
Lenny and Steve,
thank you for your responses. I updated testwise to 5.2.6, but the behaviour
does not change here.
@Lenny: Can't do component.recordError(), since i need the form component to do
so. The form component is defined a few component layers above and i would have
to pass it down as a
Hi Felix,
I remember seeing the same behaviour you mention in the past -
ValidationExceptions being handled correctly but also being logged as
an error. But I've not seen it happen in a while now and after a quick
test I'm not able to replicate it either. We're using T5.2.6, you may
want to try up
I think you can do .recordError() to do the same thing without
throwing the exception. Since no one is handling the exception in your case it
just flows to the standard error handler and sends you the email.
On Oct 1, 2011, at 12:15 PM, Felix Gonschorek wrote:
> Hi all,
>
> i encountered a
Hi all,
i encountered a undesired behaviour in our apps: When using an "validate"
component event handler that validates a single field and this handler throws an
org.apache.tapestry5.ValidationException, this exception is logged with level
ERROR:
[ERROR] ioc.Registry org.apache.tapestry5.Valid
10 matches
Mail list logo
