struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stéphane Meny (Issue Comment Edited) (JIRA) <j...@apache.org>
Subject [jira] [Issue Comment Edited] (WW-3745) Server validation potentially broken since 2.3.1
Date Tue, 17 Jan 2012 12:52:45 GMT

    [ https://issues.apache.org/jira/browse/WW-3745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13187613#comment-13187613
] 

Stéphane Meny edited comment on WW-3745 at 1/17/12 12:52 PM:
-------------------------------------------------------------

My bad, I have indeed some errors with the validators.xml adding this DTD.
Fixing and giving you the result.
                
      was (Author: smeny):
    Tested as well your DTD definition, unfortunally same issue.
                  
> 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

       

Mime
View raw message