[
https://issues.apache.org/jira/browse/WW-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187606#comment-13187606
]
Stéphane Meny commented on WW-3745:
-----------------------------------
Hello Lenart,
Today I tested the following (based on the documentation)
<!DOCTYPE validators PUBLIC "-//OpenSymphony Group//XWork Validator 1.0.2//EN"
"http://www.opensymphony.com/xwork/xwork-validator-1.0.2.dtd";>
<validators>
<field name="collaborateur.nomCollab">
<field-validator type="requiredstring">
<message key="errors.required.collab_nom" />
</field-validator>
</field>
...
Previouly we used :
<!DOCTYPE validators
PUBLIC "-//OpenSymphony Group//XWork Validator 1.0.2//EN"
"http://struts.apache.org/dtds/xwork-validator-1.0.2.dtd";>
But same issue, only way to solve was going back to 2.2.3.1 for struts2-core.
> Server validation potentially broken since 2.3.1
> ------------------------------------------------
>
> Key: WW-3745
> URL: https://issues.apache.org/jira/browse/WW-3745
> Project: Struts 2
> Issue Type: Bug
> Components: XML Validators
> Affects Versions: 2.3.1, 2.3.1.1
> Environment: Windows 7 / JDK 1.7u2 / Tomcat 7.0.24 x64 / Maven 3.0.2
> Reporter: Stéphane Meny
> Priority: Critical
> Fix For: 2.3.2
>
>
> We started to migrate our project from Struts 2.2.3.1 to 2.3.1 (also tested
> with 2.3.1.1)
> We currently use the server validation using XML validators with
> ActionClass-alias-validator.xml syntax.
> Our interceptor stack is correctly configured having :
> ...
> <interceptor-ref name="validation" />
> <interceptor-ref name="workflow" />
> ...
> Since this migration, our tests are resulting in database constraints
> violation because it seems that the validation is not called anymore.
> Problem is solved when coming back to version 2.2.3.1
> I have checked online documentation
> (http://struts.apache.org/2.3.1.1/docs/validation.html) but I can't see any
> change done from 2.2.3.1
> The only similar issue I have found is
> https://issues.apache.org/jira/browse/WW-3736 but is on Client side, could be
> a potential clue.
> Best regards,
> Stéphane
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
