On Feb 24, 2005, at 12:41 PM, Ceki G�lc� wrote:
Hi Mark,
I'd like to see log4j released for around June of this year. As such, log4j needs to enter into a consolidation and testing phase. There are a number of issues that need to be resolved. Here is a non-exhaustive list:
- Improved documentation
- More Joran tests
- Mote integration tests with Jetty and Tomcat
- Clean up filter logic and integration with LBEL
- Clean up of PatternLayout logic, better tests
- Clean up of LoggingEvent, in particular event property MDC merge logic, tests,
- faster LoggingEvent serialization possibly using a new protocol
Only the latter item involves something other then consolidation of the existing code.
I'm not fond of the signatures for the current Joran doConfigure methods and was hoping to formulate a proposal when I started looking at porting it to log4cxx. Obviously the behavior of the DOMConfiguration emulation methods can't change, however on the new methods I'd like to see an exception if there was a complete failure to configure, for example, on an attempt to configure from an nonexistent file.
Also as part of the log4cxx porting effort, I was going to look at handling multi-namespace documents. Currently, Joran behaves as if everything is in one namespace.
A pattern layout specifier for abbreviated logger and classnames (I'll follow up in another message)
To keep the list current should we create a 1.3 release issue in Bugzilla and add all of these as blocking issues?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
