One other aspect is that changes to fully support Validator 1.2.0/1.3.0 have not been ported back to Struts 1.2.x. This does not prevent upgrading to Validator 1.3.0, it just means one feature is not useable (i.e. "Variables in Resource Bundles"). More details here, in the upgrading section.
http://wiki.apache.org/jakarta-commons/ValidatorVersion120 I would recommend upgrading to Validator 1.3.0 (rather than 1.2.0) since there are a number of bug fixes in 1.3.0: http://jakarta.apache.org/commons/validator/changes-report.html Niall ----- Original Message ----- From: "Hubert Rabago" <[EMAIL PROTECTED]> Sent: Tuesday, March 28, 2006 9:32 PM The primary motivation for the recent 1.2.x releases were security issues [1] [2]. Because of this, the goal was to minimize possible upgrade issues, so the changes were limited to security fixes. The upgrade notes on the wiki for 1.2.8 and 1.2.9 [3] mentions that the user may wish to upgrade JCV as well. However, that upgrade is not required to get the security fixes. Hubert [1] http://marc.theaimsgroup.com/?l=struts-dev&m=113297746417689&w=2 [2] http://marc.theaimsgroup.com/?l=struts-dev&m=114316455208813&w=2 [3] http://wiki.apache.org/struts/StrutsUpgrade On 3/28/06, Henri Yandell <[EMAIL PROTECTED]> wrote: > Before I sit and churn through compiling and testing, does anyone know > of any blatant reasons why the Struts 1.2.x release couldn't be using > the latest FileUpload and Validator with all the bugfixes? > > (is there a convention for the [xx] part of the subject when talking > about 1.2.x?) > > Hen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
