5.很多验证标签的type已经改了,对应的param里面的name属性也改了-----针对最新版的struts。建议详细阅读struts的validation.html,在docs/docs下,比如regex对应的param的name 已经改为“regex”而不是expression了。具体的请看下面的内容。

一,转载内容
原文:http://www.blogjava.net/focusJ/archive/2010/11/15/367272.html
validation.xml 的命名规则和放置路径:
文件名:<ActionClassName>-validation.xml
例如:UserAction-validation.xml
<ActionClassName>就是要验证的Action类的名字。要将此文件放于Class文件相同的目录。
如果在Action类在struts配置中有多个action实例(actionName),那么对应某个action的验证文件名规则如下:
文件名:<ActionClassName>-<actionName>-validation.xml
例如:UserAction-login-validation.xml
(注意:上面的<aliasName>并不是method name,而是struts.xml中配置的action的name)
- <?xml version="1.0" encoding="UTF-8"?>
- <!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="username">
- <field-validator type="requiredstring"><!-- 必填字符串校验器 -->
- <param name="trim">true</param>
- <message>请填写用户名</message>
- <pre name="code" class="plain"> </field-validator>
- <field-validator type="stringlength">
- <param name="minLength">4</param>
- <param name="maxLength">32</param>
- <message>用户名长度应在4到32个字符间</message>
- </field-validator>
- </field>
- <field name="password">
- <field-validator type="requiredstring"><!-- 必填字符串校验器 -->
- <message>请填写密码</message>
- </field-validator>
- <field-validator type="stringlength"> <!-- 字符串长度校验器 -->
- <param name="minLength">6</param>
- <param name="maxLength">32</param>
- <message>为了您账号的安全,请设置6个字母以上的密码(最长可设置32个字母)</message>
- </field-validator>
- </field>
- </validators>
其实message的信息还有可以配置国际化:
配置方法也极其简单就是<message key="userpass.required"></message>,key对应的是国际化配置文件中的国际化信息。
Struts2 的验证规则大概有以下数种:
required:必填校验器
requiredstring:必填字符串校验器
int:整数校验器
double:双精度浮点数校验器
date:日期校验器
expression:表达式校验器
fieldexpression:字段表达式校验器
email:电子邮件校验器
url:网址校验器
visitor:Visitor校验器
conversion:转换校验器
stringlength:字符串长度校验器
regex:正则表达式校验器
1。必填检验
<validators>
<field-validator type="required">
<message>指定检验失败的提示信息</message>
</field-validator>
</field>
</validators>
2。必填字符串检验
<validators>
<field name="username">
<field-validator type="requiredstring">
<param name="trim">true</param>
<message>指定检验失败的提示信息</message>
</field-validator>
</field>
</validators>
3。整数检验器/浮点检验
<validators>
<field name="age">
<field-validator type="int">
<param name="min">1</param>
<param name="max">150</param>
<message>年纪必须在1到150之间</message>
</field-validator>
</field>
</validators>
<validators>
<field name="birth">
<field-validator type="date">
<param name="min">1900-01-01</param>
<param name="max">2050-02-21</param>
<message key="birth.range"/>
</field-validator>
</field>
</validators>
5.字段表达式检验器(要求指定字段满足一个逻辑表达式)
<validators>
<field name="re_pass">
<param name="expression"> (pass eq re_pass)</param>
<message>密码必须和确认密码相等</message>
</field-validator>
</field>
</validators>
6.邮件地址校验
<validators>
<field name="email">
<field-validator type="email">
<message>你的电子邮件地址必须是一个有效的电邮地址</message>
</field-validator>
</field>
</validators>
<validators>
<field name="url">
<field-validator type="url">
<message>你的主页地址必须是一个有效的网址</message>
</field-validator>
</field>
</validators>
8.字符串长度检验
<validators>
<field name="user">
<param name="minlength">4</param>
<param name="maxlength">20</param>
<message>你的用户名长度必须在4到20之间</message>
</field-validator>
</field>
</validators>
9.正则表达式检验
<validators>
<field name="user">
<field-validator type="regex">
<param name=" regex "><![CDATA[(\w{4,25})]]></param>
<message>您输入的用户名只能是字母和数组,且长度必须在4到25之间</message>
</field-validator>
</field>
</validators
接下来我举一个简单的登录验证的例子:
- <%@ page language="java" import="java.util.*" pageEncoding="UTF-8"%>
- <%@ taglib uri="/struts-tags" prefix="s"%>
- <%
- String path = request.getContextPath();
- String basePath = request.getScheme() + "://"
- + request.getServerName() + ":" + request.getServerPort()
- + path + "/";
- %>
- <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
- <html>
- <head>
- <base href="<%=basePath%>">
- <title>My JSP 'fail.jsp' starting page</title>
- <meta http-equiv="pragma" content="no-cache">
- <meta http-equiv="cache-control" content="no-cache">
- <meta http-equiv="expires" content="0">
- <meta http-equiv="keywords" content="keyword1,keyword2,keyword3">
- <meta http-equiv="description" content="This is my page">
- </head>
- <body>
- <s:form action="user/login.action" validate="true">
- <table
- style="border-style: solid; border-color: lightblue; position: absolute; top: 30px">
- <tbody>
- <tr>
- <td>
- <div
- style="margin-center: 32px; border-style: solid; border-color: lightblue; border-width: 2px;">
- <a>用户名:</a>
- <input id="username" name="user.name" type="text" />
- </div>
- </td>
- </tr>
- <tr>
- <td>
- <div
- style="margin-center: 32px; border-style: solid; border-color: lightblue; border-width: 2px">
- <a>密 码:</a>
- <input id="password" name="user.password" type="password" />
- </div>
- </td>
- </tr>
- <!-- 弹出出错信息 -->
- <tr>
- <td>
- <div id="msg"><s:fielderror/></div>
- </td>
- </tr>
- <tr>
- <td>
- <div>
- <span><input id="submit" type="submit" value="登录" />
- </span>
- </div>
- </td>
- </tr>
- </tbody>
- </table>
- </s:form>
- </body>
- </html>
这里有个地方需要注意:form中要加入validate=“true”这个属性。
***Action-validation.xml
- <?xml version="1.0" encoding="UTF-8" ?>
- <!DOCTYPE validators PUBLIC
- "-//OpenSymphony Group//XWork Validator 1.0//EN"
- "http://www.opensymphony.com/xwork/xwork-validator-1.0.2.dtd" >
- <validators >
- <field name ="user.name" >
- <field-validator type ="requiredstring">
- <message key="username.required"></message>
- </field-validator>
- </field>
- <field name ="user.password" >
- <field-validator type ="requiredstring">
- <message key="userpass.required"></message>
- </field-validator>
- </field>
- </validators>
***Action.action这个挺简单的就是常规的action写法,在execute中验证表单,或自己封装方法验证表单,但是不能继承validate()方法,因为action执行的时候实现检察validate方法的,如果这样的话就配置重复了,不过有什么结果我没有测试(没啥意义)。
struts.xml配置
- <constant name="struts.custom.i18n.resources" value="globalMessages"></constant>
- <include file="defaule.xml" />
- <!-- 有关用户的操作 -->
- <package name="user" extends="struts-default" namespace="/user">
- <action name="login" class="bbs.action.UserAction">
- <result name="success">/system/list.action</result>
- <result name="input">/login.jsp</result>
- </action>
- </package>
二,自己总结
1.struts2的输入校验主要包括以下的类型,他们的名字及对应的类如下所示。
-
"1.0" encoding="UTF-8" xml version=
-
-
-
-
-
<validators>
-
<validator name="required" class="com.opensymphony.xwork2.validator.validators.RequiredFieldValidator"/>
-
<validator name="requiredstring" class="com.opensymphony.xwork2.validator.validators.RequiredStringValidator"/>
-
<validator name="int" class="com.opensymphony.xwork2.validator.validators.IntRangeFieldValidator"/>
-
<validator name="long" class="com.opensymphony.xwork2.validator.validators.LongRangeFieldValidator"/>
-
<validator name="short" class="com.opensymphony.xwork2.validator.validators.ShortRangeFieldValidator"/>
-
<validator name="double" class="com.opensymphony.xwork2.validator.validators.DoubleRangeFieldValidator"/>
-
<validator name="date" class="com.opensymphony.xwork2.validator.validators.DateRangeFieldValidator"/>
-
<validator name="expression" class="com.opensymphony.xwork2.validator.validators.ExpressionValidator"/>
-
<validator name="fieldexpression" class="com.opensymphony.xwork2.validator.validators.FieldExpressionValidator"/>
-
<validator name="email" class="com.opensymphony.xwork2.validator.validators.EmailValidator"/>
-
<validator name="url" class="com.opensymphony.xwork2.validator.validators.URLValidator"/>
-
<validator name="visitor" class="com.opensymphony.xwork2.validator.validators.VisitorFieldValidator"/>
-
<validator name="conversion" class="com.opensymphony.xwork2.validator.validators.ConversionErrorFieldValidator"/>
-
<validator name="stringlength" class="com.opensymphony.xwork2.validator.validators.StringLengthFieldValidator"/>
-
<validator name="regex" class="com.opensymphony.xwork2.validator.validators.RegexFieldValidator"/>
-
<validator name="conditionalvisitor" class="com.opensymphony.xwork2.validator.validators.ConditionalVisitorFieldValidator"/>
-
</validators>
2.校验文件可以使用国际化提示信息,只需要在对应的.properties文件中添加好键值对,然后在验证文件中使用即可。比如,提示信息message标签,可以这么写<message key="name.regex"/>,其中name.regex为国际化信息文件中的内容。
3.校验器可以有两种风格,上面转载的是字段(field)校验器风格,还有非字段校验器风格,如下所示(当然,最外层也是<validators>标签
-
<validator type="expression>
-
<param name=" expression">foo gt bar </param>
-
<message>foo must be great than bar. </message>
-
</validator>
-
<validator type="required">
-
<param name="fieldName">bar </param>
-
<message>You must enter a value for bar. </message>
-
</validator>
-
<validator type="校验器名">
-
<param name="fieldName">需要被校验的字段 </param>
-
<!-- 可以有0个或多个 -->
-
<param name="参数名">参数值 </param>
-
<message>You must enter a value for bar. </message>
-
</validator>
4.短路校验器:默认都是短路的,如果没有短路,在validator标签(非字段风格)或者field-validator标签(字段风格)增加属性short-circuit="true"即可
5.很多验证标签的type已经改了,对应的param里面的name属性也改了-----针对最新版的struts。建议详细阅读struts的validation.html,在docs/docs下。
6.最新的内建校验器:
(1)conversion校验器
-
<validators>
-
...
-
<field name="myIntegerField">
-
<field-validator type="conversion">
-
<param name="repopulateField">true </param>
-
<message>Conversion Error (Integer Wanted) </message>
-
</field-validator>
-
</field>
-
...
-
</validators>
-
-
-
<pre>
-
<!-- Plain Validator Syntax -->
-
<validator type="conversion">
-
<param name="fieldName">myField </param>
-
<message>Conversion Error Occurred </message>
-
</validator>
-
-
<!-- Field Validator Syntax -->
-
<field name="myField">
-
<field-validator type="conversion">
-
<message>Conversion Error Occurred </message>
-
</field-validator>
-
</field>
-
</pre>
(2)date 校验器
-
<validators>
-
<!-- Plain Validator syntax -->
-
<validator type="date">
-
<param name="fieldName">birthday </param>
-
<param name="min">01/01/1990 </param>
-
<param name="max">01/01/2000 </param>
-
<message>Birthday must be within ${min} and ${max} </message>
-
</validator>
-
-
<!-- Field Validator Syntax -->
-
<field name="birthday">
-
<field-validator type="date">
-
<param name="min">01/01/1990 </param>
-
<param name="max">01/01/2000 </param>
-
<message>Birthday must be within ${min} and ${max} </message>
-
</field>
-
</field>
-
-
<!-- Field Validator Syntax with expression -->
-
<field name="birthday">
-
<field-validator type="date">
-
<param name="minExpression">${minValue} </param> <!-- will be evaluated as: Date getMinValue() -->
-
<param name="maxExpression">${maxValue} </param> <!-- will be evaluated as: Date getMaxValue() -->
-
<message>Age needs to be between ${min} and ${max} </message>
-
</field-validator>
-
</field>
-
</validators>
(3)double 验证器
-
<validators>
-
<!-- Plain Validator Syntax -->
-
<validator type="double">
-
<param name="fieldName">percentage </param>
-
<param name="minInclusive">20.1 </param>
-
<param name="maxInclusive">50.1 </param>
-
<message>Age needs to be between ${minInclusive} and ${maxInclusive} (inclusive) </message>
-
</validator>
-
-
<!-- Field Validator Syntax -->
-
<field name="percentage">
-
<field-validator type="double">
-
<param name="minExclusive">0.123 </param>
-
<param name="maxExclusive">99.98 </param>
-
<message>Percentage needs to be between ${minExclusive} and ${maxExclusive} (exclusive) </message>
-
</field-validator>
-
</field>
-
-
<!-- Field Validator Syntax with expression -->
-
<field name="percentage">
-
<field-validator type="double">
-
<param name="minExclusiveExpression">${minExclusiveValue} </param> <!-- will be evaluated as: Double getMinExclusiveValue() -->
-
<param name="maxExclusiveExpression">${maxExclusiveValue} </param> <!-- will be evaluated as: Double getMaxExclusiveValue() -->
-
<message>Percentage needs to be between ${minExclusive} and ${maxExclusive} (exclusive) </message>
-
</field-validator>
-
</field>
-
</validators>
(4)email验证器
-
<!-- Plain Validator Syntax -->
-
<validators>
-
<validator type="email">
-
<param name="fieldName">myEmail </param>
-
<message>Must provide a valid email </message>
-
</validator>
-
</validators>
-
-
<!-- Field Validator Syntax -->
-
<field name="myEmail">
-
<field-validator type="email">
-
<message>Must provide a valid email </message>
-
</field-validator>
-
</field>
-
-
<!-- Field Validator Syntax with expressions -->
-
<!-- Only available when used with xml based configuration, if you want to have the same
-
flexibility with annotations use @RegexFieldValidator instead -->
-
<field name="myEmail">
-
<field-validator type="email">
-
<param name="regexExpression">${emailPattern} </param> <!-- will be evaluated as: String getEmailPattern() -->
-
<param name="caseSensitiveExpression">${emailCaseSensitive} </param> <!-- will be evaluated as: boolean getEmailCaseSensitive() -->
-
<param name="trimExpression">${trimEmail} </param> <!-- will be evaluated as: boolean getTrimEmail() -->
-
<message>Must provide a valid email </message>
-
</field-validator>
-
</field>
(5)expression验证器
-
<validators>
-
<validator type="expression">
-
<param name="expression"> .... </param>
-
<message>Failed to meet Ognl Expression .... </message>
-
</validator>
-
</validators>
(6)fieldexpression 验证器
-
<!-- Plain Validator Syntax -->
-
<validators>
-
<!-- Plain Validator Syntax -->
-
<validator type="fieldexpression">
-
<param name="fieldName">myField </param>
-
<param name="expression"><![CDATA[#myCreditLimit > #myGirfriendCreditLimit]]> </param>
-
<message>My credit limit should be MORE than my girlfriend </message>
-
<validator>
-
-
<!-- Field Validator Syntax -->
-
<field name="myField">
-
<field-validator type="fieldexpression">
-
<param name="expression"><![CDATA[#myCreditLimit > #myGirfriendCreditLimit]]> </param>
-
<message>My credit limit should be MORE than my girlfriend </message>
-
</field-validator>
-
</field>
-
-
</vaidators>
(7)int 验证器
-
<validators>
-
<!-- Plain Validator Syntax -->
-
<validator type="int">
-
<param name="fieldName">age </param>
-
<param name="min">20 </param>
-
<param name="max">50 </param>
-
<message>Age needs to be between ${min} and ${max} </message>
-
</validator>
-
-
<!-- Field Validator Syntax -->
-
<field name="age">
-
<field-validator type="int">
-
<param name="min">20 </param>
-
<param name="max">50 </param>
-
<message>Age needs to be between ${min} and ${max} </message>
-
</field-validator>
-
</field>
-
-
<!-- Field Validator Syntax with expression -->
-
<field name="age">
-
<field-validator type="int">
-
<param name="minExpression">${minValue} </param> <!-- will be evaluated as: Integer getMinValue() -->
-
<param name="maxExpression">${maxValue} </param> <!-- will be evaluated as: Integer getMaxValue() -->
-
<message>Age needs to be between ${min} and ${max} </message>
-
</field-validator>
-
</field>
-
</validators>
(8)regex验证器
-
<validators>
-
<!-- Plain Validator Syntax -->
-
<validator type="regex">
-
<param name="fieldName">myStrangePostcode </param>
-
<param name="regex"><![CDATA[([aAbBcCdD][123][eEfFgG][456])]]> </param>
-
</validator>
-
-
<!-- Field Validator Syntax -->
-
<field name="myStrangePostcode">
-
<field-validator type="regex">
-
<param name="regex"><![CDATA[([aAbBcCdD][123][eEfFgG][456])]]> </param>
-
</field-validator>
-
</field>
-
-
<!-- Field Validator Syntax with expressions -->
-
<field name="myStrangePostcode">
-
<field-validator type="regex">
-
<param name="regexExpression">${regexValue} </param> <!-- will be evaluated as: String getRegexValue() -->
-
<param name="caseSensitiveExpression">${caseSensitiveValue} </param> <!-- will be evaluated as: boolean getCaseSensitiveValue() -->
-
<param name="trimExpression">${trimValue} </param> <!-- will be evaluated as: boolean getTrimValue() -->
-
</field-validator>
-
</field>
-
</validators>
(9)required验证器
-
<validators>
-
-
<!-- Plain Validator Syntax -->
-
<validator type="required">
-
<param name="fieldName">username </param>
-
<message>username must not be null </message>
-
</validator>
-
-
-
<!-- Field Validator Syntax -->
-
<field name="username">
-
<field-validator type="required">
-
<message>username must notbe null </message>
-
</field-validator>
-
</field>
-
-
</validators>
(10)requiredstring 验证器
-
<validators>
-
<!-- Plain-Validator Syntax -->
-
<validator type="requiredstring">
-
<param name="fieldName">username </param>
-
<param name="trim">true </param>
-
<message>username is required </message>
-
</validator>
-
-
<!-- Field-Validator Syntax -->
-
<field name="username">
-
<field-validator type="requiredstring">
-
<param name="trim">true </param>
-
<message>username is required </message>
-
</field-validator>
-
</field>
-
-
<!-- Field-Validator Syntax with expression -->
-
<field name="username">
-
<field-validator type="requiredstring">
-
<param name="trimExpression">${trimValue} </param> <!-- will be evaluated as: boolean getTrimValue() -->
-
<message>username is required </message>
-
</field-validator>
-
</field>
-
</validators>
(11)short验证器
-
<validators>
-
<!-- Plain Validator Syntax -->
-
<validator type="short">
-
<param name="fieldName">age </param>
-
<param name="min">20 </param>
-
<param name="max">50 </param>
-
<message>Age needs to be between ${min} and ${max} </message>
-
</validator>
-
-
<!-- Field Validator Syntax -->
-
<field name="age">
-
<field-validator type="short">
-
<param name="min">20 </param>
-
<param name="max">50 </param>
-
<message>Age needs to be between ${min} and ${max} </message>
-
</field-validator>
-
</field>
-
-
<!-- Field Validator Syntax with expression -->
-
<field name="age">
-
<field-validator type="short">
-
<param name="minExpression">${minValue} </param> <!-- will be evaluated as: Short getMinValue() -->
-
<param name="maxExpression">${maxValue} </param> <!-- will be evaluated as: Short getMaxValue() -->
-
<message>Age needs to be between ${min} and ${max} </message>
-
</field-validator>
-
</field>
-
</validators>
(12)stringlength 验证器
-
<validators>
-
<!-- Plain Validator Syntax -->
-
<validator type="stringlength">
-
<param name="fieldName">myPurchaseCode </param>
-
<param name="minLength">10 </param>
-
<param name="maxLength">10 </param>
-
<param name="trim">true </param>
-
<message>Your purchase code needs to be 10 characters long </message>
-
</validator>
-
-
<!-- Field Validator Syntax -->
-
<field name="myPurchaseCode">
-
<field-validator type="stringlength">
-
<param name="minLength">10 </param>
-
<param name="maxLength">10 </param>
-
<param name="trim">true </param>
-
<message>Your purchase code needs to be 10 characters long </message>
-
</field-validator>
-
</field>
-
-
<!-- Field Validator Syntax with expression -->
-
<field name="myPurchaseCode">
-
<field-validator type="stringlength">
-
<param name="minLengthExpression">${minLengthValue} </param> <!-- will be evaluated as: Integer getMinLengthValue() -->
-
<param name="maxLengthExpression">${maxLengthValue} </param> <!-- will be evaluated as: Integer getMaxLengthValue() -->
-
<param name="trimExpression">${trimValue} </param> <!-- will be evaluated as: boolean getTrimValue() -->
-
<message>Your purchase code needs to be 10 characters long </message>
-
</field-validator>
-
</field>
-
</validators>
(13)url验证器
-
<!-- Plain Validator Syntax -->
-
<validator type="url">
-
<param name="fieldName">myHomePage </param>
-
<message>Invalid homepage url </message>
-
</validator>
-
-
<!-- Field Validator Syntax -->
-
<field name="myHomepage">
-
<field-validator type="url">
-
<message>Invalid homepage url </message>
-
</field-validator>
-
</field>
-
</validators>
(14)visitor验证器
-
<validators>
-
<!-- Plain Validator Syntax -->
-
<validator type="visitor">
-
<param name="fieldName">user </param>
-
<param name="context">myContext </param>
-
<param name="appendPrefix">true </param>
-
</validator>
-
-
<!-- Field Validator Syntax -->
-
<field name="user">
-
<field-validator type="visitor">
-
<param name="context">myContext </param>
-
<param name="appendPrefix">true </param>
-
</field-validator>
-
</field>
-
</validators>
(15)conditionalvisitor验证器
-
<field name="colleaguePosition">
-
<field-validator type="conditionalvisitor">
-
<param name="expression">reason == 'colleague' and colleaguePositionID == 'OTHER' </param>
-
<message>You must select reason Colleague and position Other </message>
-
</field-validator>
-
</field>
-