http://struts.apache.org/1.2.4/userGuide/dev_validator.html#i18n
On Thu, Mar 1, 2012 at 4:02 PM, joann luo <joannlu...@gmail.com> wrote: > Hello, Dave: > > Thanks for pointing this out. > > I am working on a customer issue reported from a project that we released > quite a while ago. I won't be able to upgrade the struts JAR in this case. > > Since I have to stay with validator 1.1.3 is there any other way to provide > customized error message for "errors.required", "errors.invalid" cases > instead of using the out-of-box > ones? > > Thanks again, > Joann > > On Thu, Mar 1, 2012 at 3:41 PM, Dave Newton <davelnew...@gmail.com> wrote: > > > You can't just update a validation DTD and expect everything to suddenly > > use a later version of the validation libraries. S1.2.4, AFAIK, uses > > validator 1.1.3. Hence all S1.2.4 code will be written assuming > > commons-validator 1.1.3. > > > > Capabilities introduced in later versions of commons-validator would > > require deploying said later version. Any S1 interactions with > > commons-validator, however, would remain at the 1.1.3 level. If it's a > > validator-only issue, it *may* still work, but if the new functionality > > relies on any S1 interaction, I'm pretty sure it wouldn't. > > > > Dave > > > > On Thu, Mar 1, 2012 at 3:33 PM, joann luo <joannlu...@gmail.com> wrote: > > > > > Hello, > > > > > > I am sorry about the confusion before. > > > > > > I searched web app's component.xml file and found the following, > > therefore, > > > we are actually using Struts1.2.4 in this project. > > > > > > <dependency name="prereqs.sn/struts.minimal" type="jar" > version="1.2.4" > > /> > > > <dependency name="prereqs.sn/struts.extra" type="jar" version="1.2.4" > /> > > > > > > Per my previous email, even though I updated the validation.xml and > > > validator-rules.xml to point to validator_1_3_0.dtd, the bundle > attribute > > > still does not work. > > > > > > Is there any other way to provide customized error message for > > > "errors.required", "errors.invalid" cases instead of using the > out-of-box > > > ones? > > > > > > Thanks a lot > > > Joann > > > > > > On Thu, Mar 1, 2012 at 12:04 PM, Jeffrey Black <jeffblack...@gmail.com > > > >wrote: > > > > > > > Hi Joann, > > > > > > > > Can you please confirm what version of Struts you are using? > > > > > > > > You appear to be using Struts 2 for your application [1]; however it > > > > appears you are referencing Struts 1.x validation information. > Perhaps > > > I'm > > > > missing something? > > > > > > > > [1] > > > > > > > > > > > > > > http://struts.1045723.n5.nabble.com/How-to-implement-alternate-error-messages-in-the-Struts-validation-framework-Struts-2-0-1-4-td5522076.html > > > > > > > > Best, > > > > > > > > jb > > > > > > > > On Thu, Mar 1, 2012 at 8:59 AM, joann luo <joannlu...@gmail.com> > > wrote: > > > > > > > > > Hello, > > > > > I am using > > > http://jakarta.apache.org/commons/dtds/validator_1_3_0.dtdbut > > > > > I > > > > > found it still does not honor ‘bundle” attribute in the > > validation.xml. > > > > > > > > > > I need to display an alternate error message defined in a custom > > > > > bundle through the Struts validation framework instead of the > default > > > > > error message. Based on the information provided from this early > > > > > thread, it should have been available since Validator 1.1.4. > > > > > > > > > > http://www.mail-archive.com/user@struts.apache.org/msg23694.html > > > > > If this is still not supported in validator_1_3_0.dtd, then is > there > > > any > > > > > way to implement this? > > > > > > > > > > > > > > > > > > > > > > > > > I appreciate any advice you may have. > > > > > > > > > > > > > > > > > > > > Thank you. > > > > > > > > > > > > > > >
