Julian Gosnell wrote:
> Have you given the log4j/jdk1.4 logging argument
> thought ?
My 2c worth is that if you want the best logging mechanism, then
you would use the org.mortbay.util stuff :-) So it is really
a discussion of standards. I have added jdk1.4 logging support
simply on the basis that it is standard - not due to any particular
technical merit.
People are welcome to contribute a log4jLogSink if they want one.
> Integrating the two is going to be a problem for many
> projects, including JBoss/Jetty - so I would be
> interested to hear about available approaches...
Well if they are well designed, then you should be able to
mix and match log sources and log sinks. It was fairly
trivial to put Jetty logs into the JBoss mechanism or the
1.4 sinks.
As far as JBoss is concerned, at the minimum, we probably
want:
+ 1.4 Logger Handler to take log events from user code and feed
it into the JBoss log mechanism.
+ 1.4 Logger as a sink of JBoss log events, so that all JBoss events
are sent to it.
+ Ditto for log4j if you want.
But anyway, I really didn't want to start the "which log" debate as I
am sure it has been batted about several times already.
However, I do think that somebody needs to think about how to include code
that uses 1.4 features (whatever they are) in a way that does not break
the build for 90% of current users.
So we need a build environment that can handle optional 1.4 support before
we work out which 1.4 features will be used.
cheers
--
Greg Wilkins<[EMAIL PROTECTED]> GB Phone: +44-(0)7092063462
Mort Bay Consulting Australia and UK. Mbl Phone: +61-(0)4 17786631
http://www.mortbay.com AU Phone: +61-(0)2 98107029
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
