Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 29370 invoked from network); 4 Sep 2002 17:50:01 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 4 Sep 2002 17:50:01 -0000 Received: (qmail 28475 invoked by uid 97); 4 Sep 2002 17:50:33 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 28465 invoked by uid 97); 4 Sep 2002 17:50:32 -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 26250 invoked by uid 98); 4 Sep 2002 17:25:13 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3D7641E9.7080108@apache.org> Date: Wed, 04 Sep 2002 13:24:57 -0400 From: Jean-Francois Arcand User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jakarta Commons Developers List Subject: Re: digester 2.0 [WAS Re: [digester] [PROPOSAL] More pattern matching flexibility] References: <2B65F403-BEC0-11D6-8363-003065DC754C@blueyonder.co.uk> <3D74BF9B.8010704@gmx.de> <3D74D195.1000307@gmx.de> <3D762C19.8070606@gmx.de> <3D762E1E.90008@apache.org> <3D764012.8030109@gmx.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Christopher Lenz wrote: > Jean-Francois Arcand wrote: > >> Christopher Lenz wrote: >> >>> After some more fiddling I think we can get this implemented without >>> breaking binary compatibility. Well, almost: The field >>> Digester.rules is the only remaining problem. It'd need to be >>> removed or at least ignored by Digester, both possibly breaking >>> clients who used the field directly to get/set the Rules instance >>> from a subclass. >>> >>> I've got Digester working with the Matcher interface, and all of the >>> unit tests still run without modifications. >>> >>> I'm not sure where to go from here... One could argue that >>> backwards-compatibility is pretty much preserved with the changes, >>> so this stuff could even go into a 1.x release, and a subsequent 2.0 >>> release would be a cleanup release, removing all the deprecated stuff. >> >> >> Not sure I like the "pretty much preserved" :-) Like you said, the >> Digester.rules is a problem (maybe small, maybe not). I would prefer >> adding your work under 2.0. > > > Okay, I definitely appreciate the conservative point of view ;-) > > Having so many protected members in such a central and exposed class > can really have a negative impact on further development... reducing > the exposure of instance variables would IMHO be a very important > point to consider for Digester 2.0. > > BTW, Jean-Francois, you've added the XML Schema support, right? Is > there any reason why Digester.JAXP_SCHEMA_LANGUAGE is neither static > nor final? Yes, the goal was to be able to use the parser with another schema language (ex: http://www.ascc.net/xml/resource/schematron/schematron.html) or a user-defined schema language. BTW, the way I name the variable is misleading since uppercase is usually used for final/static variable... -- Jeanfrancois > > -- To unsubscribe, e-mail: For additional commands, e-mail: