You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Lukasz Lenart (JIRA)" <ji...@apache.org> on 2013/01/03 12:26:12 UTC

[jira] [Resolved] (WW-3904) Remove parse param and allow unconditionally parse all the params of validator

     [ https://issues.apache.org/jira/browse/WW-3904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lukasz Lenart resolved WW-3904.
-------------------------------

    Resolution: Won't Fix
      Assignee: Lukasz Lenart

parse param should stay as thus allow backward compatibility and also not everyone wants to use expressions
                
> Remove parse param and allow unconditionally parse all the params of validator
> ------------------------------------------------------------------------------
>
>                 Key: WW-3904
>                 URL: https://issues.apache.org/jira/browse/WW-3904
>             Project: Struts 2
>          Issue Type: Sub-task
>          Components: XML Validators
>    Affects Versions: 2.3.7
>            Reporter: Lukasz Lenart
>            Assignee: Lukasz Lenart
>            Priority: Minor
>             Fix For: 2.3.9
>
>
> Right now there is a parse param when set to true enable expression evaluation in params, like ${max} or ${min}. Annotation based configuration doesn't use it, only XML based configuration and it's unneeded overhead.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira