Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 98199 invoked from network); 11 Nov 2004 17:05:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 11 Nov 2004 17:05:31 -0000 Received: (qmail 41520 invoked by uid 500); 11 Nov 2004 17:05:29 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 41411 invoked by uid 500); 11 Nov 2004 17:05:29 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 41392 invoked by uid 99); 11 Nov 2004 17:05:29 -0000 Received-SPF: pass (hermes.apache.org: domain of niall.pemberton@blueyonder.co.uk designates 195.188.213.8 as permitted sender) Received: from [195.188.213.8] (HELO smtp-out5.blueyonder.co.uk) (195.188.213.8) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 11 Nov 2004 09:05:28 -0800 Received: from DELL1800 ([82.43.169.235]) by smtp-out5.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.6713); Thu, 11 Nov 2004 17:05:52 +0000 Message-ID: <003f01c4c811$9a65f970$0200a8c0@DELL1800> From: "Niall Pemberton" To: "Commons Developers Jakarta" Subject: [Validator] Next Release Date: Thu, 11 Nov 2004 17:12:20 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-OriginalArrivalTime: 11 Nov 2004 17:05:52.0405 (UTC) FILETIME=[B328E450:01C4C810] X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I decided to have a go a resolving a couple of Struts bugs to do with bundles/resources and validator: http://issues.apache.org/bugzilla/show_bug.cgi?id=18169 http://issues.apache.org/bugzilla/show_bug.cgi?id=21760 Currently theres an inconsitency in how Struts handles bundles since although the validator dtd allows users to specify alternative bundles - Struts completely ignores them. Seems to me this is a big weakness in how handles Strut's bundles if validator can't take acount of them. Specifically Struts ignores the following validator DTD attributes: * the msg elements 'bundle' attribute * the msg elements 'resource' attribute * the arg elements 'bundle' attribute Fixing Struts required a couple of small changes to Commons Validator, which I've just done - it was already subject to the following outstanding bugzilla request: http://issues.apache.org/bugzilla/show_bug.cgi?id=29452 In order to now fix Struts there needs to be a release of Commons Validator with this change in and I'm wondering about the following: 1) Version 1.1.4 or Version 1.2.0 ======================== I wan't sure what the difference between the whats in the HEAD (Version 1.2.0) and the VALIDATOR_1_1_2_BRANCH (Version 1.1.3) - but from a quick scan a summary of the differences is: * Form Inheritance functionality (new extends attribute) * Loads of deprecations removed (including arg0 to arg3) * A number of minor bug fixes I guess it would be good to have only one branch and release Version 1.2.0 but I'm wondering whether the Form Inheritance is fully tested and working and also, given all the deprecations removed, whether it might be better (upgrade wise for the users) to release Version 1.1.4 from the VALIDATOR_1_1_2_BRANCH. 2) Arg's Position Parameter - Bug 31194 ============================== While doing this stuff on validator I came across the following enhancement request: http://issues.apache.org/bugzilla/show_bug.cgi?id=31194 It looked like a good idea and I've attached a patch for review which implements this request. Personally, if the decision is to go with a Version 1.2.0 release - I wouldn't want to upgrade to 1.2.0 without this enhancement being applied - when replacing arg0 - arg3 I could get away with not having to add a position attribute if this enhacement was done. The easiest route - Struts wise is to go the Version 1.1.4 route. It would mean zero impact on the users, except having to drop the new jar in. Validator wise, we should probably get the Version 1.2.0 out of the door and just support one version. I'd rather go the 1.1.4 route but I'd appreciate hearing what others think. Niall --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org