Re: [jboss-as7-dev] EJB3 subsystem and a different kind of logging mess

+1 I think this was just an oversight. Stuart On 04/05/2012, at 10:57 PM, David M. Lloyd wrote: > On 05/04/2012 06:37 AM, Jaikiran Pai wrote: >> I just noticed that the i18n loggers in EJB3 subsystem have >> "org.jboss.ejb3" category [1] (and child categories [2]) instead of >> "org.jboss.as.ejb3". The non-i18n logging, in EJB3 subsystem, that >> happens using the usual Logger.getLogger(className) way (obviously) uses >> the org.jboss.as.ejb3 category. So this effectively means that the user >> has to end up configuring multiple different categories for logging from >> the EJB3 subsytem classes. Was it intentional to use "org.jboss.ejb3" >> category for i18n logging? I see that some other subsystems rightly use >> org.jboss.as.xxx category for i18n. Is it too late to change this for >> EJB3 subsystem now? > > I think we should definitely change these to org.jboss.as.ejb3. It's > not a component upgrade so it should be merge-worthy. Also the problem > is probably only in a few places. > -- > - DML > _______________________________________________ > jboss-as7-dev mailing list > jboss-as7-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-as7-dev _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev