Hi All, If we do logging, JUL is acceptable of course. So is commons-logging.
When it is integration time, we'll need some guidance even if it is just pointers to HOW-TOs. In my case, what happens when my server to coded to Log4J and I want all logging to go to the same file? I do not need an answer now but it will be an issue. Gary On Fri, Feb 10, 2012 at 8:25 AM, Jörg Schaible <joerg.schai...@scalaris.com>wrote: > Hi, > > ma...@apache.org wrote: > > > Gary Gregory <garydgreg...@gmail.com> wrote: > > > >>On Feb 10, 2012, at 5:39, Mark Thomas <ma...@apache.org> wrote: > >> > >>> On 10/02/2012 00:20, Simone Tripodi wrote: > >>>> I have a preference fo juli. > >>> I can work with that. > >> > >>Is a dependency on JULI better than on common-logging? > >> > >>Or is there some confusion talking about JUL vs JULI? > > > > I was assuming java.util.logging rather than Tomcat's logging library > > JULI. > > And how do you intend then to manage the log output in an enterprise > environment? Implement an own JUL-fomatter, deploy it with your web > application and try to use it. > > - Jörg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > -- E-Mail: garydgreg...@gmail.com | ggreg...@apache.org JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0 Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK Blog: http://garygregory.wordpress.com Home: http://garygregory.com/ Tweet! http://twitter.com/GaryGregory
