> > we not only need to add an IoC adapter between the Avalon container
> > and Commons component, but we need some way of integrating the
> > component into a logging framework.
> Yep I realized this too. However the best approach is to use the Monitor
> concept for these components. I think James Strachan already did so with
> his ThreadPool implementation.
There are places in Commons classes where they use System.out.println rather
than a logger. In other cases, they have a PrintWriter, but that's it. No
concept of log level, for example. You don't know the context in which the
messages are being written, deep in the core of some Commons class. So the
addition of logging or monitoring still means making a change.
I'm not saying we shouldn't do it. I'm setting an expectation of something
that will need to be addressed in order to do it properly.
As for James' ThreadPool, (a) it is in sandbox; (b) it is in sandbox because
Doug Lea's util.concurrent is mature, useful and the basis for JSR 166; (c)
James' monitor is just an exception handler. It isn't really suitable in
the current form for other monitoring.
--- Noel
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
