> I think this s**ks too, and I am wondering what to do about it. The best
> idea I had so far, although I haven't figured out how to implement it, is
> to use log4j if it is available, otherwise the printwriter. As far as I
> can tell the ra "vendor" is not actually required to write anything onto
> the printwriter, maybe ignoring it completely is the best policy.
Perhaps, I thought that we could use the stream adapter, thus converting
calls to the PrintWriter into Log4j calls, but then we loose control over
priorities and such. For stuff that is going to live in JBoss I would just
use Log4j.
> Do you know of a good way to tell if log4j is available?
Not really, you could try a Class.forName("org.apache.log4j.Category");, but
I would just assume Log4j, as trying to get around it would be a mess.
--jason
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
