Return-Path: 
 <commons-dev-return-17585-qmlist-jakarta-archive-commons-dev=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-dev-archive@apache.org
Received: (qmail 48764 invoked from network); 14 Oct 2002 20:19:02 -0000
Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131)
  by daedalus.apache.org with SMTP; 14 Oct 2002 20:19:01 -0000
Received: (qmail 16066 invoked by uid 97); 14 Oct 2002 20:19:35 -0000
Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org
Received: (qmail 15997 invoked by uid 97); 14 Oct 2002 20:19:34 -0000
Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:commons-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:commons-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:commons-dev-help@jakarta.apache.org>
List-Post: <mailto:commons-dev@jakarta.apache.org>
List-Id: "Jakarta Commons Developers List" <commons-dev.jakarta.apache.org>
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Delivered-To: mailing list commons-dev@jakarta.apache.org
Received: (qmail 15883 invoked by uid 98); 14 Oct 2002 20:19:33 -0000
X-Antivirus: nagoya (v4218 created Aug 14 2002)
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
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:18:39 -0700
Message-ID: <458473676F1AC74A84EAB2F22004DA6D5312E9@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: AcJzvWSAbeRfgbAaSayn8uJmERse4QAAWviw
From: "Scott Sanders" <ssanders@nextance.com>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Can you explain the property 0 thing a little more?  I don't understand =
why Digester cannot handle it.

Thanks,
Scott

> -----Original Message-----
> From: Ceki G=FClc=FC [mailto:ceki@qos.ch]=20
> Sent: Monday, October 14, 2002 1:07 PM
> To: Jakarta Commons Developers List; Jakarta Commons Developers List
> Subject: Re: [joran] example (was Re: [Latka][Proposal] Make=20
> Jelly a required dependency?)
>=20
>=20
>=20
> Here is a sample log4j config file in XML:
>=20
> <?xml version=3D"1.0" encoding=3D"UTF-8" ?>
> <!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
>=20
> <log4j:configuration debug=3D"true"
>                       =
xmlns:log4j=3D'http://jakarta.apache.org/log4j/'>
>=20
>    <appender name=3D"CON" class=3D"org.apache.log4j.ConsoleAppender">
>      <param name=3D"Threshold" value=3D"INFO"/>
>      <layout class=3D"org.apache.log4j.PatternLayout">
>        <param name=3D"ConversionPattern" value=3D"%5p [%t] %c - =
%m%n"/>
>      </layout>
>    </appender>
>=20
>    <appender name=3D"FOO" class=3D"org.apache.log4j.FileAppender">
>      <param name=3D"File" value=3D"foo.log"/>
>      <layout class=3D"org.apache.log4j.PatternLayout">
>        <param name=3D"ConversionPattern" value=3D"%r %p %t %c - =
%m%n"/>
>      </layout>
>    </appender>
>=20
>    <appender name=3D"UNUSED" =
class=3D"org.apache.log4j.net.SMTPAppender">
>      <param name=3D"To" value=3D"ceki@apache.org"/>
>      <param name=3D"Host" value=3D"xyz.com"/>
>      <layout class=3D"org.apache.log4j.HTMLLayout"/>
>    </appender>
>=20
>    <logger name=3D"com.foo">
>      <level value =3D"info" />
>      <appender-ref ref=3D"FOO" />
>    </logger>
>=20
>    <root>
>      <level value =3D"debug" />
>      <appender-ref ref=3D"CON" />
>    </root>
> </log4j:configuration>
>=20
>=20
> The noteworthy point is that the appender element is used=20
> only if root or a logger element references it. For example,=20
> the UNUSED appender, which is not referenced by any root or=20
> logger element, will not be created nor configured. I call=20
> this the 0th Property.
>=20
> Property 0: It's the root or loggers elements which "drive"
> the appender elements.
>=20
> Another interesting point is that different appender elements=20
> may have different nested elements which must be evaluated=20
> differently. For example,
>=20
>    <appender name=3D"EMAIL" =
class=3D"org.apache.log4j.net.SMTPAppender">
>      <param name=3D"To" value=3D"ceki@apache.org"/>
>      <param name=3D"Host" value=3D"xyz.com"/>
>      <layout class=3D"org.apache.log4j.HTMLLayout"/>
>      <trigger class=3D"org.apache.log4j.someClass">   <--- trigger is =
a=20
> special tag
>          <param name=3D"maxCount" value=3D"1000"/>
>      </trigger>
>    </appender>
>=20
> <trigger> is an SMTPAppender specific tag.
>=20
> Another example,
>=20
>    <appender name=3D"ROLLING" =
class=3D"org.apache.log4j.RollingAppender">
>      <param name=3D"File" value=3D"comfoo.log"/>
>      <layout class=3D"org.apache.log4j.PatternLayout">
>        <param name=3D"ConversionPattern" value=3D"%r %p %t %c - =
%m%n"/>
>      </layout>
>      <rolloverStrategy class=3D"org.apache.log4j.SizeStrategy">=20
>  <-- special tag
>        <param name=3D"maxSize" value=3D"100KB"/>
>      </rolloverStrategy>
>      <namingStrategy class=3D"org.apache.log4j.SuffixStrategy">=20
>  <-- special tag
>        <param name=3D"type" value=3D"numerical"/>
>        <param max=3D"max" value=3D"-1"/>
>      </rolloverStrategy>
>    </appender>
>=20
> in the above example <rolloverStrategy> and <namingStrategy>=20
> are RollingAppender specific tags.
>=20
> Log4j could support such tags using the addXXX paradigm that=20
> Ant uses for its tasks.
>=20
> The remaining desired properties are
>=20
> 1) low redundancy in the processing code
>=20
> 2) ability to parse totally unknown tags that are *not*
> nested within primary level tasks, e.g. <root>, <logger>,=20
> <appender> tags.
>=20
> I think that a rule based system such as Digester can take=20
> care of properties 1 and 2 but not property 0 defined above.=20
> Can jelly?
>=20
> BTW, am I making any sense?
>=20
> At 17:00 14.10.2002 +0100, James Strachan wrote:
> >From: "Ceki G=FClc=FC" <ceki@qos.ch>
> > >> Have you any examples of what joran
> > >>might look like yet?
> > >
> > > No, I do not have examples, except in my head.
> >
> >Any chance you could type a snippet of an example thats in your head=20
> >down in an email; I'm interested to hear what you were thinking of.
> >
> > > Moreover, one wonders at the
> > > sanity of the Joran enterprise when a library like Jelly=20
> is already=20
> > > available.
> >
> >Jelly can be molded into many shapes via libraries so maybe=20
> Jelly could=20
> >implement Joran; however thats purely an implementation detail. Lets=20
> >ponder a little on what Joran could look like to an end user first=20
> >before worrying about such details.
> >
> >James
> >-------
> >http://radio.weblogs.com/0112098
>=20
> --
> Ceki
>=20
> TCP implementations will follow a general principle of=20
> robustness: be conservative in what you do, be liberal in=20
> what you accept from others. -- Jon Postel, RFC 793
>=20
>=20
>=20
> --
> To unsubscribe, e-mail:  =20
> <mailto:commons-dev-> unsubscribe@jakarta.apache.org>
> For=20
> additional commands,=20
> e-mail: <mailto:commons-dev-help@jakarta.apache.org>
>=20
>=20

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>