logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Womack <mwom...@bevocal.com>
Subject Things to do (was RE: Acorn Progress)
Date Wed, 09 Apr 2003 22:57:32 GMT
Paul,

3 things come to mind immediately.

- Implement support for logging event properties in XMLLayout &
PatternLayout, similar to the changes you made for MDC.
- The MDC changes in XMLLayout and PatternLayout still have some open issues
(primarily with the test cases) which are mentioned in the bug (I forget the
bug number).
- If you would like to review the Plugin/PluginRegistry/Receiver
code/design, I would appreciate a second pair of eyes. I (really) need to
start the watchdog stuff, which is again going to use the plugin base.

I'm sure there is more stuff to do.  Ceki?

-Mark

> -----Original Message-----
> From: Paul Smith [mailto:Paul.Smith@lawlex.com.au]
> Sent: Wednesday, April 09, 2003 3:29 PM
> To: 'Log4J Developers List'
> Subject: RE: Acorn Progress
> 
> 
> Hey Mark, while we're waiting to get the new bits and pieces 
> of Chainsaw
> into CVS, anything I can help out with?
> 
> cheers,
> 
> Paul
> 
> > -----Original Message-----
> > From: Mark Womack [mailto:mwomack@bevocal.com]
> > Sent: Thursday, 10 April 2003 3:00 AM
> > To: 'Log4J Developers List'
> > Subject: RE: Acorn Progress
> > 
> > 
> > No.  Plugins are new to v1.3 and can be defined in the xml 
> > configuration
> > files.  Plugins are classes that can take action to 
> > affect/use/modify a
> > given logger repository.  For example, "receiver" are a type 
> > of plugin that
> > receives external/remote logging events and "posts" them to 
> > the local logger
> > repository.  "watchdog" plugins will (when I get off my butt 
> > and write them)
> > "watch" a configuration source (file, url, socket, etc) and 
> > when it changes
> > reconfigure the repository with the new settings.
> > 
> > Similar to appenders, they can have their own configuration points.
> > Examples in the current cvs are SocketReciever, 
> SocketHubReceiver, and
> > JMSReceiver.
> > 
> > -Mark
> > 
> > > -----Original Message-----
> > > From: RBair@dtint.com [mailto:RBair@dtint.com]
> > > Sent: Wednesday, April 09, 2003 9:47 AM
> > > To: Log4J Developers List
> > > Subject: RE: Acorn Progress
> > > 
> > > 
> > > By "plugins" do you mean the configuration gui for user 
> > > defined appenders? 
> > >  I haven't tackled that piece yet. 
> > > 
> > > Richard
> > > 
> > > 
> > > 
> > > 
> > > Mark Womack <mwomack@bevocal.com>
> > > 04/08/2003 08:41 PM
> > > Please respond to "Log4J Developers List"
> > >  
> > >         To:     'Log4J Developers List' 
> > <log4j-dev@jakarta.apache.org>
> > >         cc: 
> > >         Subject:        RE: Acorn Progress
> > > 
> > > 
> > > Looks like a good start.  How about configuration for plugins?
> > > 
> > > -Mark
> > > 
> > > > -----Original Message-----
> > > > From: Richard Bair [mailto:rbair23@yahoo.com]
> > > > Sent: Tuesday, April 08, 2003 10:43 AM
> > > > To: log4j
> > > > Subject: Acorn Progress
> > > > 
> > > > 
> > > > Hey Everyone,
> > > > 
> > > > I'm sure not getting much time to work on this, but
> > > > slow and steady wins the race, right? :-)
> > > > 
> > > > Attached is a screenshot of where I'm at right now. 
> > > > You can see the basic idea.  I think using a JList
> > > > like this is a little unconventional, but I didn't
> > > > like the idea of using two JLists etc.  Just playing
> > > > around a little bit there.
> > > > 
> > > > Also, I'm reading XML config files just fine here. 
> > > > Its really a suprisingly compact piece of code so far.
> > > >  I still have a long way to go!
> > > > 
> > > > Sorry about the size/quality of that image, maybe its
> > > > time I download some better image product than Paint.
> > > > 
> > > > Cheers,
> > > > Richard
> > > > 
> > > > __________________________________________________
> > > > Do you Yahoo!?
> > > > Yahoo! Tax Center - File online, calculators, forms, and more
> > > > http://tax.yahoo.com
> > > > 
> > > 
> > > 
> > > 
> > 
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: log4j-dev-help@jakarta.apache.org
> > > 
> > > 
> > > 
> > 
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: log4j-dev-help@jakarta.apache.org
> > 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: log4j-dev-help@jakarta.apache.org
> 
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: log4j-dev-help@jakarta.apache.org


Mime
View raw message