sounds good for me. Thanks David! - Romain
2012/1/26 David Blevins <[email protected]> > > On Jan 26, 2012, at 12:47 PM, David Blevins wrote: > > > > > On Jan 26, 2012, at 10:08 AM, Romain Manni-Bucau wrote: > > > >> normally the default logging should simply be a JUL logging. > >> > >> the only modification is if you don't override OpenEJB root loggers > >> (OpenEJB, Transaction...) the handler (=appender) is changed to look > like > >> the old noe in embedded mode (=not standalone tomee). > >> > >> As David said he restored the old log4j feature so you can do > >> -Dopenejb.log.factory=log4j > >> or -Dopenejb.log.factory=slf4j. > >> > >> I don't think we should look the classloader too much to guess what the > >> user want. Tomcat, cxf, ... uses jul by default and that's fine so why > >> couldn't we do the same? > >> > >> Why should we need log4j today? > >> > >> ok to keep as few differences as before with the embedded case but > >> "technically" i wouldn't depend on log4j anymore. > > > > Added some features here for users along the lines mentioned. > > > > https://issues.apache.org/jira/browse/OPENEJB-1760 > > > > If someone is using Log4j syntax and we cannot respect that, we will now > log messages to system.out explicitly saying that the settings will be > ignored. > > > > Come to think about it I need to tweak that... One sec... > > Refined the logic. It's now pretty simple. > > 1) log4j is the default if you are using log4j syntax. Otherwise it's > JULI. > > 2) If log4j syntax is in use and we are not using log4j, we will warn you > using whatever logging is enabled that your log4j settings are ignored and > we will list each and every single log4j setting that we are ignoring and > where we got it from. > > So there should be no quiet failing and no need to go digging through docs > to figure out how to get the desired outcome. > > > -David > >
