http://bugzilla.slf4j.org/show_bug.cgi?id=257
Ralph Goers <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #6 from Ralph Goers <[email protected]> 2012-05-10 08:02:51 CEST --- Here is another perspective. Logger names are primarily used to choose the configuration that will apply to the specific events being logged. While class names are one good way of doing that there is absolutely nothing wrong with using some other scheme as long as it meets your requirements on filtering, appender selection and ultimately publishing the events. That said, as was noted logger names are hierarchical. Names like Billing, Billing.Automatic and Billing.Recurrent only make sense if that hierarchy meets your requirements. Providing a patch with examples is probably the best way for you to get this issue resolved. -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ slf4j-dev mailing list [email protected] http://mailman.qos.ch/mailman/listinfo/slf4j-dev
