Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 46753 invoked from network); 11 Oct 2002 16:37:29 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 11 Oct 2002 16:37:29 -0000 Received: (qmail 9323 invoked by uid 97); 11 Oct 2002 16:38:15 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 9307 invoked by uid 97); 11 Oct 2002 16:38:15 -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 9294 invoked by uid 98); 11 Oct 2002 16:38:14 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-Id: <5.1.0.14.0.20021011183021.0213ce88@mail.qos.ch> X-Sender: ceki@mail.qos.ch X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 11 Oct 2002 18:37:27 +0200 To: "Jakarta Commons Developers List" From: Ceki =?iso-8859-1?Q?G=FClc=FC?= Subject: Re: DOM-based Digester? In-Reply-To: <20021011092600.I18344-100000@icarus.apache.org> References: <5.1.0.14.0.20021011180521.0210cc68@mail.qos.ch> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Craig, One can (easily?) convert a DOM tree into a SAX event stream but that's not what I had meant. I meant writing a new tool leveraging the DOM api to perform rule based XML processing a la commons-digester. Has anyone given that some thought? At 09:27 11.10.2002 -0700, Craig R. McClanahan wrote: >On Fri, 11 Oct 2002, Ceki G=FClc=FC wrote: > > > Date: Fri, 11 Oct 2002 18:21:09 +0200 > > From: Ceki G=FClc=FC > > Reply-To: Jakarta Commons Developers List= > > To: commons-dev@jakarta.apache.org > > Subject: DOM-based Digester? > > > > > > Has anyone thought of implementing Digester type functionality using the > > DOM API? > > > >I've never needed that, but in principle it sounds feasible -- all you'd >need is something to convert the DOM into a stream of SAX events and you >could reuse all the existing machinery. I'm sure that problem has been >solved by somebody before. > > > > > -- > > Ceki > >Craig -- Ceki TCP implementations will follow a general principle of robustness: be conservative in what you do, be liberal in what you accept from others. -- Jon Postel, RFC 793 -- To unsubscribe, e-mail: For additional commands, e-mail: