I'm not going to argue for one over the other. Where I work we use log4j exclusively and I never had the time to get the lowdown other than that log4j supported a richer set of appenders and apparently made it easier to write your own. When this thread started, I decided to do a search and I found this link that helped me understand the differences.
http://www.ingrid.org/jajakarta/log4j/jakarta-log4j-1.1.3/docs/critique.html Up front, this fellow is biased, but he does a pretty fair job of comparing the differences and making a compelling case for the superiority of log4j (I think). You can decide for yourself. There seem to be a couple of options for those wishing to use log4j: 1) 'Plug in' a replacement logger. Based on Jerome's description, this looks like a lot of work and may be fragile across versions. 2) Somehow restructure the Restlet logging mechanism so that plugging in is easier and explicitly supported. 3) Disable existing logger and wedge in your own. 4) Bridge the two. The last is what I'm doing but I'm not exactly sure how :-( I was given a code snippet that did the magic using an internal class we have. I'm pretty busy right now, but I'll see if I can get something out here that at least describes how it works. I believe this approach simply redirects JSR 47 logging into our log4j log and we write all our stuff into our logs too. That may not be ideal, nor may it be the reality. I'll get back... Sean
