[Red5] Problems with W3CAppender
mondain at gmail.com
Fri Jun 6 09:47:07 PDT 2008
I'm trying to make this new logging stuff as painless as possible, I know it
would suck to have to change all your classes..
On Fri, Jun 6, 2008 at 9:12 AM, Daniel Rossi <electroteque at gmail.com> wrote:
> On 07/06/2008, at 1:50 AM, Mondain wrote:
> I think I've got that down..
> Ok :)
> What I have found is that the "problem" is/was partly the classloader and
> commons logging. One of the first things that happens when you start the
> server is that the Spring ClassUtils is called which tries to create an
> Apache commons logger, this in turn causes a static logfactory to be spawned
> in slf4j. The log factory creates a "default" logger context that holds all
> the loggers. A logger is "found" by using a selector, so I've had to create
> a selector specifically for Red5 since the Default and JNDI implementations
> dont work well for us. I'm going to stop rambling now since its probably way
> too much detail for most...
> No no thats perfect. You are the guru and I'm the student :)
> On last item though.. the developer responsible for log4j, slf4j, and
> logback has stated that "we" should not use the static logger pattern
> private static Logger log = LoggerFactory.getLogger(MyClass.class);
> that we should instead use
> private Logger log = LoggerFactory.getLogger(MyClass.class);
> doing this is supposed to some how relieve us of our logger issues.
> Ok does that mean a complete refactor in all classes and webapps ?
> Red5 mailing list
> Red5 at osflash.org
It is difficult to free fools from the chains they revere. - Voltaire
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Red5