I think LogKit and Log4J are both great and external interface is pretty similar. How about Avalon providing a logger service that maps to LogKit and can also map to Log4J. That way a user can configure whatever one likes. It may be good to have LogKit as a separate project and peer of Log4J. Let the non Avalon users pick what they like. I personally find LogKit Simpler and easier to follow but Log4J more powerful. There is a time and place for both and why choose one over other. I am sure the talented developers of both the Toolkits have numerous Noospheres to conquer. :-) The source is Open so one can add features and tests from one toolkit to another, and still keep it separate. I don't think it is worth picking winners, when the life of either toolkit could exceed our lifetime. Harmeet One philosophy, if you forgive my ranting: 'If you go walk away from a big hill, it becomes smaller.' :-)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
