IIUC, the validation ID is only allocated by the first instance if the
AbstractField class and is backed by a thread-local value. If the
component renders multiple times, it uses the same validation ID in
every iteration.
I've tried to fix it (by including the validation ID in the Setup
ComponentAction), haven't got it to work yet.
Am 21.01.2015 um 17:19 schrieb Jochen Kemnade:
Am 20.01.2015 um 10:30 schrieb Apache Jenkins Server:
Tapestry Bean Validatior Integration Tests >
org.apache.tapestry5.beanvalidator.integration.TapestryBeanValidationIntegrationTests.beaneditform_validation
FAILED
java.lang.AssertionError at
TapestryBeanValidationIntegrationTests.java:93
Tapestry Bean Validatior Integration Tests >
org.apache.tapestry5.beanvalidator.integration.TapestryBeanValidationIntegrationTests.beaneditor_validation
FAILED
java.lang.AssertionError at
TapestryBeanValidationIntegrationTests.java:251
Anyone got an idea why these fail?
Somehow the validation messages get mixed up, the message for the
password field is shown for both the user name and the password field
(see attached screenshot).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
