[ http://issues.apache.org/struts/browse/SHALE-325?page=comments#action_38607 ] Rahul Akolkar commented on SHALE-325: -------------------------------------
Try again, it works for me. And adding <message-bundle> should, since the method in question looks up the application's message bundle for the "msg" attribute of (in this case, the custom) <validator>. The "message" attribute of <val:commonsValidator> gets priority, if present (which is nice, since it allows to change the "default" error message for the custom, or "built-in", validator). On a separate note, we could do better than an NPE here, let me take a stab at that. > Add a custom validation example to the Use Cases example app > ------------------------------------------------------------ > > Key: SHALE-325 > URL: http://issues.apache.org/struts/browse/SHALE-325 > Project: Shale > Issue Type: Improvement > Components: Validator > Reporter: Wendy Smoak > Priority: Minor > Fix For: 1.0.4-SNAPSHOT > > > Add an example of using a custom validator to the Commons Validator > Integration section of the use-cases example app. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
