I was referring to this mail [1] when I mentioned commons logging and SLF4J. I don't know if its worth converting if you've already used LOG4J. SLF4J does have some nice features though, particularly parameterized log messages. You can read all about it at: http://www.slf4j.org.
...ant On 4/18/07, Kevin Williams <[EMAIL PROTECTED]> wrote:
Is SLF4J a better route than Log4j? If so, I wonder if we should convert over the RDB DAS. On 4/18/07, ant elder <[EMAIL PROTECTED]> wrote: > > On 4/17/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote: > > <snip/> > > I found our current Monitor stuff difficult to follow as well. I suggest > > that we start a new discussion thread to discuss monitoring in general, > > and try to come up with something that will be more usable and easier to > > adopt through our whole runtime. > > > Starting the new thread for you... > > I agree we should improve monitoring and logging in the runtime. > > I've used AOP before for this type of thing, its cool, but it does add yet > another new thing to know about which could be off putting for new > developers. How about just using one of the existing logging packages that > most people are already completely familiar with? Commons Logging looks > like > its coming to its end, no one really likes java.util.logging, so how about > SLF4J, its really easy and nice to use? > > I also think exception handling could be improved, I don't find the > current > exception formatter design easy to use, and most times stack traces end up > missing the important bit of information you need. How about just using > the > traditional way of putting everything in the exception message and using > properties files to allow for I18N? > > One thing I've wondered about was having a release specifically targeting > these RAS type features. So once we've worked out the strategy for > logging, > exceptions, internationalization etc we have a release where a big focus > is > on implementing/fixing/testing all these RAS things. > > ...ant >
