On Apr 30, 2008, at 12:50 PM, Henrib wrote:
the rant is on the containers not doing the
right thing by incorporating (something like) JULI.
Containers {w,sh}ould not have to invent specific and proprietary
if JDK
logging specified a way to define LogManager per class-loader;
imho, the
rant is squarely on Sun
It seems to me Sun left it wide open for a thousand implementations
to flourish, actually. What's to prevent a ClassLoader specific
LogManagerManager from being put into the mix? Nothing - that's what
JULI does. Container writers do need to ensure they funnel all of
their plugged in components to a unified pipeline to be good logging
citizens.
Erik
