On Dec 11, 2007 6:00 PM, David M. Lloyd <david.lloyd(a)redhat.com> wrote:
* The JBossAS logging system must be changed such that BY DEFAULT
log
messages are all handled properly (in terms of category and level),
regardless of the logging framework used (java.util.logging or log4j).
No, relying on the System.out/System.err capture mechanism is NOT
sufficient for this task. This means that, as far as I can tell, we
should always be installing a JUL LogManger on appserver startup.
Frankly it really baffles and disappoints me that 4.0.x and 4.2.x didn't
do this out of the box.
I have a LogManager that uses the context CL to find its configuration
and isolate logging:
http://anonsvn.jboss.org/repos/jbossweb/trunk/java/org/apache/juli/ClassL...
It could be used as a starting point or for some ideas.
Rémy