Oops! I'm a goose..... should have been www.log4j.org
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Rob Castaneda
Sent: Friday, August 25, 2000 12:41 PM
To: jBoss
Subject: RE: [jBoss-User] Logging
what about log4java? www.log4java.org
They have done a lot of thinking on it's framework, maybe some ideas....
You can control patterns of what you want displayed and configure different
appenders for where you want the logs directed
do you guys have any thoughts on this?
-Rob
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of marc fleury
Sent: Friday, August 25, 2000 12:26 PM
To: jBoss
Subject: RE: [jBoss-User] Logging
we can do better with a JMS based logger, where we provide "filters".
We had such code demoing at JavaOne, and I am thinking about open sourcing
it... worked with SpyderMQ
marc
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Dan Christopherson
> Sent: Friday, August 25, 2000 10:57 AM
> To: jBoss
> Subject: Re: [jBoss-User] Logging
>
>
> I see four log levels as minimal, rather than complex. Right now on my
> project we're using 6: Trace, Debug, Info, Warn, Error, Critical.
>
> Granted, this works best if you have an infrastructure that lets you split
> things up according to level (and facility is even better)
>
> On Fri, 25 Aug 2000, Sebastien Alborini wrote:
>
> > Hi,
> >
> > I think the logging process is too complex (four levels, Information
> > Error Debug Warning), and few people use this complexity in jboss code.
> > I would propose only 2 levels:
> > - Information-Error always printed
> > - Debug-Warning printed only if debug flag is true, this flag would be a
> > parameter of ConsoleLogging (or Logger?), and could be toggled through
> > jmx (let's advertise localhost:8082 !)
> >
> > We should also review the code to see what we really want to print.
> > Any comments?
> >
> > Sebastien
> >
> >
> >
> > Rickard �berg wrote:
> > >
> > > Hi!
> > >
> > > Justin Forder wrote:
> > > > Are there any documentation conventions for MLETs?
> > > >
> > > > A good UNIX configuration file would be largely composed of
> explanatory
> > > > text and commented-out examples.
> > >
> > > IMHO the current MLet conf style is seriously flawed. Not only is it a
> > > bad thing to have anonymous <ARG TYPE=.. VALUE=..> tags (which is
> > > which!?) but the JMX RI also does not support comments(!) in the file.
> > > Because of this I would generally recommend that MLets do not take any
> > > arguments, but instead are configure through get/set methods, whose
> > > values are set through the .jcml file (which do not have the above
> > > problems!).
> > >
> > > When I get the time I will convert as many MBeans as possible
> to support
> > > this style of configuration.
> > >
> > > regards,
> > > Rickard
> > >
> > > --
> > > Rickard �berg
> > >
> > > Email: [EMAIL PROTECTED]
> > > http://www.telkel.com
> > > http://www.jboss.org
> > > http://www.dreambean.com
> > >
> > > --
> > > --------------------------------------------------------------
> > > To subscribe: [EMAIL PROTECTED]
> > > To unsubscribe: [EMAIL PROTECTED]
> > > Problems?: [EMAIL PROTECTED]
> >
> >
> > --
> > --------------------------------------------------------------
> > To subscribe: [EMAIL PROTECTED]
> > To unsubscribe: [EMAIL PROTECTED]
> > Problems?: [EMAIL PROTECTED]
> >
>
> --
> Dan Christopherson (danch)
> STR Technical Architect (www.str.com)
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
