(Redirecting response to user list where this type of question belongs...)
You can swap in the new validator version without any changes to the rest of your application; the commons-validator team run a regression test at the binary level. This page has a complete list of what jars need to be updated: http://wiki.apache.org/jakarta-commons/ValidatorVersion120 We upgraded to 1.2 validator in struts 1.2.8 and only had to update 2 JARs, collections and beanutils. Note that the MANIFEST.MF in the 1.7 version of beanutils says that it is 1.6.2, the best way to see what version you have is to either compare the size of the jar file with that on an official commons-beanutils download site, or run 'sum' or 'md5sum' on the jar file and compare it to the md5sum on the commons-beanutils download site. -ed On 10/23/06, Enzo <[EMAIL PROTECTED]> wrote:
Excuse my dropping in the matter... I am not so experienced on the versions of the various jars, but I have got the same problem with struts custom validator, tiles ecc... my question is: is it possible to raise the commons validator version to solve this problem and not to raise also the struts version ? without impacts ? is there a sort of compatibility matrix for the various jars? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
