Marc wanted Jetty rebranded as JBossWeb. All I have done is change the word "Jetty" to "JBossWeb" in the Jetty logging bridge. Since Jetty does not use log4j internally, no class names are available, so everything was being output to the "Jetty" category, now it is being output to the "JBossWeb" category.
The word "Jetty" only ever loosely concurred with the name of the class giving the output...... You will notice that the jetty-plugin.sar is now the jbossweb.sar and that Jetty MBeans now try to advertise themselves as JBossWeb. If that doesn't confuse all the users - nothing will :-) Jules Jason Dillon wrote: > Looks like we are regressing back to the previous logging chaos? well > not completely. > > > > Why are we using fictitious logger names instead using the class name > where the logger resides? > > > > I guess on the side, why have we renamed Jetty to JBossWeb? > > > > Let?s not undo all of the hard work we have done to clean up the logging > usage inside of JBoss3. > > > > --jason > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Stuff, things, and much much more. http://thinkgeek.com/sf _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
