Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 86584 invoked from network); 6 Mar 2004 22:37:40 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 6 Mar 2004 22:37:40 -0000 Received: (qmail 60798 invoked by uid 500); 6 Mar 2004 22:37:23 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 60743 invoked by uid 500); 6 Mar 2004 22:37:23 -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 60726 invoked from network); 6 Mar 2004 22:37:22 -0000 Received: from unknown (HELO smtp-out7.blueyonder.co.uk) (195.188.213.10) by daedalus.apache.org with SMTP; 6 Mar 2004 22:37:22 -0000 Received: from [10.0.0.2] ([82.38.65.173]) by smtp-out7.blueyonder.co.uk with Microsoft SMTPSVC(5.0.2195.5600); Sat, 6 Mar 2004 22:37:27 +0000 Mime-Version: 1.0 (Apple Message framework v612) In-Reply-To: References: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable From: robert burrell donkin Subject: Re: [Digester] New rules Date: Sat, 6 Mar 2004 22:37:25 +0000 To: "Jakarta Commons Developers List" X-Mailer: Apple Mail (2.612) X-OriginalArrivalTime: 06 Mar 2004 22:37:27.0469 (UTC) FILETIME=[9A453DD0:01C403CB] X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On 4 Mar 2004, at 07:59, J=F6rg Schaible wrote: > Simon Kitching wrote on Wednesday, March 03, 2004 11:54 PM: >> In some ways it's nice, >> because it is obvious to users, but of course every rule >> added to Digester increases the jar size, the API complexity, >> and the maintenance load. > > Will this be addressed in Digester2 ? I was really astonished, that=20 > the digester itself has a method for any known rule. This makes the=20 > usage of self-written ones not too obvious. Personally I would=20 > eliminate/deprecate all of them and just offer addRule. But this is=20 > getting OT for this thread, for D2 I have other annotations anyway :) users pretty much demand that these methods are added. the problem is that these methods do introduce an unhelpful coupling=20 and add to the footprint. it's just one of those things that's=20 unfortunate but probably not positively harmful. one of the solutions that i've been turning over in my mind would be to=20= introduce a DigesterEngine superclass that would be a minimal=20 stripped-down version without the dependency on those rules. that could=20= be done without breaking backwards compatibility. on the other hand,=20 i've never felt motivated to add this since it's not really an itch for=20= me. - robert= --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org