Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 76688 invoked from network); 14 Oct 2002 20:48:25 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 14 Oct 2002 20:48:25 -0000 Received: (qmail 17268 invoked by uid 97); 14 Oct 2002 20:49:15 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 17222 invoked by uid 97); 14 Oct 2002 20:49:14 -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 17167 invoked by uid 98); 14 Oct 2002 20:49:14 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Content-Class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [joran] example (was Re: [Latka][Proposal] Make Jelly a required dependency?) X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 Date: Mon, 14 Oct 2002 13:48:22 -0700 Message-ID: <458473676F1AC74A84EAB2F22004DA6D5312EA@mail.nextance.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [joran] example (was Re: [Latka][Proposal] Make Jelly a required dependency?) thread-index: AcJzwZ04o13rJdxoQsOdeLzVMOyGBgAAOiPQ From: "Scott Sanders" To: "Jakarta Commons Developers List" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > Property 0 says that parsing of appender tags are driven by=20 > logger tags. For example, the following config script does nothing. OK, I think I understand now. > > >=20 > >=20 > > > > > > > >=20 > In particular, the CONSOLE appender is not created because no=20 > logger references it. Gotcha. > Property 0 requires the XML processor to access elements that=20 > have been already defined. With Digester which is SAX based,=20 > there is no way for a rule to trigger parsing of an element=20 > that was already parsed by the SAX parser. In other words,=20 > using SAX you cannot access elements backwards or forwards.=20 > You only have access to the current element. Please correct=20 > me if I am wrong. You are not wrong, the only way to do this would be to force loggers to come first, or build everything and then throw it away if you don't need it. Another way would be to cache the elements and then refire them if you find a logger that needs them. Is there anyway to create and throw away an appender? Or to require that loggers come first? The other way would be to cache the appender nodes somehow in a custom rule, that is then accessible when the time comes to need to load it. Am I making sense now? So, the default Digester setup cannot do this, unless you are willing to construct and then throwaway unnecessary objects. Cheers, Scott -- To unsubscribe, e-mail: For additional commands, e-mail: