Using fancy reflection, buffered appender or some other magically logging fluff?
Does this mean we will add log4j-core.jar to the main lib/ directory too? --jason On Fri, 7 Dec 2001, Scott M Stark wrote: > > I have this working and I'll check it in tomorrow after some more testing. > > ----- Original Message ----- > From: "Jason Dillon" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Thursday, December 06, 2001 9:24 PM > Subject: Re: [JBoss-dev] jboss-boot.jar & log4j > > > > That would be good assuming that we get as far as loading the Log4j > service, > > if we don't then we don't have any logging information about the problem. > > Plus todo that we still need the log4j core classes... and well, we would > > also need our proxy generator since the log4j bits are not interfaces and > > thus we can't make use of the java.lang.reflect.Proxy bits. > > > > I think that we might want to create a buffered appender, have the default > > configuration log to System.out, then once the service is up, flush the > > buffer to the users configured appenders and remove it. > > > > --jason > > > > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
