Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 81896 invoked from network); 11 Oct 2002 23:37:22 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 11 Oct 2002 23:37:22 -0000 Received: (qmail 2587 invoked by uid 97); 11 Oct 2002 23:38:12 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 2571 invoked by uid 97); 11 Oct 2002 23:38:12 -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 2556 invoked by uid 98); 11 Oct 2002 23:38:12 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-Id: <5.1.0.14.0.20021012013437.02180e68@mail.qos.ch> X-Sender: ceki@mail.qos.ch X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sat, 12 Oct 2002 01:37:23 +0200 To: "Jakarta Commons Developers List" From: Ceki =?iso-8859-1?Q?G=FClc=FC?= Subject: Re: DOM-based Digester? In-Reply-To: <3DA72CDD.10602@apache.org> References: <5.1.0.14.0.20021011180521.0210cc68@mail.qos.ch> <5.1.0.14.0.20021011184606.02160ce0@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 Yes, this is precisely one of the advantages of DOM trees. You can easily=20 deal with backward or forward references to other elements. Backward=20 references are useful for lazy instantiation as you have mentioned. At 15:56 11.10.2002 -0400, Jean-Francois Arcand wrote: >One interesting uses is to create object "on demand", meaning not only=20 >during the parsing of the file, but anytime you need to create an object=20 >(you keep the DOM tree in memory). This mean you can applies more that one= =20 >object to the same set of rules without having to re-parse the file. You=20 >just cache the dom tree in the Digester and re-use it when the parse=20 >method is invoked. > >-- Jeanfrancois > >Ceki G=FClc=FC wrote: > >> >>At 00:37 12.10.2002 +0800, John Yu wrote: >> >>>At 12:21 am 12-10-2002, you wrote: >>> >>>>Has anyone thought of implementing Digester type functionality using=20 >>>>the DOM API? >>> >>> >>>Just curious: why does one need that? >> >> >>Because rule based processing is useful regardless of whether SAX or DOM= =20 >>is being used. One objective advantage is that you can add new rules=20 >>dynamically. You cannot do that with compiled Java. >> >>>-- >>>John Yu >> >> >>-- >>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:= >>so > > > >-- >To unsubscribe, e-mail: = >For additional commands, e-mail:= > -- 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: