Hi folks!
Browsing over the logging mechanism in JDK 1.4, I found to my
surprise
that logger hyerarchy is reversed: parents know about children, but
children do not have access to their parents.
This is the exact reverse of what class hyerarchies have done since
Modula-2. It seems illogical: children loggers must know what logger
they come from, and parents do not need to access to children
information.
This point is well done in log4j, and so it would seem practical to
adopt it as a standard. log4j has worked like a charm for us in our
project, and its license is very convenient. So I take the liberty to
suggest using it as a standard logging mechanism; or at least specify
a
set of interfaces based on it, so that 3rd parties (including log4j's
creator) can build and ship their own implementation, a la J2EE.
Thanks for your attention,
Alex Fernández.