Hi Berin, > From: Berin Loritsch > Sent: Monday, March 24, 2003 3:27 PM [...] > I recently made an alteration to Fortress (about a week ago) that > altered the way it decided what the root category was going to be. > Previously, it assigned the root category to the LoggerManager--but > that required all logger categories to decend from "fortress.*". > Now the kernel uses its "fortress" logger tree as expected, and the > components live in there own space.
I use a snapshot of Excalibur from some weeks ago. So my version should build hierarchies beneath Fortress ... > Also, the way logger names are assigned (I looked deeper into the > code), is based on the component id, not the logger attribute. Hmm. This might be a problem for me. I adjusted the component's ids to reflect some kind of selection in already existing data. Therefore my ids often do not follow that hierarchical naming scheme with the dots. Even more, since I am running in a servlet container that already uses Log4J and supports this in an external IDE, I will try to integrate into their hierarchy at a later time switching also to Log4J. I might have a look into the code. Basically the logger attribute could be respected if it is present and the id is used only as default. How are the logger categories controlled in Merlin and Phoenix? Maybe I can support something general. Is the "log-level" attribute in the xconf supported then? Regards, J�rg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
