3 Replies Latest reply on Apr 25, 2007 11:16 AM by Matt Drees

    trace level logging on Jboss AS

    Matt Drees Master

      From looking at the Log4JProvider class, it looks like log.trace simply does a log.debug call (log4j doesn't have trace). I'd like to be able to differentiate between trace and debug, but I don't see an easy way to do that. If I could override Log4JProvider, I could have "trace" do something besides log.debug, but it doesn't look like we can plug in our own LogProviders.

      If it isn't too much work, could we be given control of which LogProvider Seam uses? I imagine it'd be hard to make it a component, because logging needs to be available before components are loaded; but there is probably another way.

      If that isn't going to happen, can anyone suggest a workaround to enable trace logging?