[Opensource] Commons Logger Rehash....

[larry hamel]

Hi Mike,

I recall voting to stick with log4j previously because I didn't want to change my code, and I figured log4j would continue to be a better logging system.

However, you make it sound like the initialization will be handled either framework, and that my code doesn't need to change.

If so, then the switch sounds good to me.

Larry

At 07:45 PM 2/19/2003, you wrote:
>Hey All,
>
>I'm thinking once again of switching the 5.1 code over to commons logger where the framework takes over strict initialization of the library to save some people's grief.  Underneath, I'm still planning on using log4j... I like logfactor5, and chainsaw as tools, and JDK 1.4 doesn't even come close.
>
>Ok, now onto my reasoning.  In the past, when a spec initially doesn't hold up, we've painted ourselves into a corner by following strictly another spec and not allowing for other technologies to replace the initial decision.  This is especially true when you have corporate developers who are looking to follow 'J2EE strictly'.
>
>So I've been thinking to myself that it won't be long before somebody wants to use JDK 1.4 logging instead of log4j, "Because it is standard".... By having expresso internally use Commons API for its logging API they can easily do what they want with about 2 lines of code changed.
>
>Furthermore the Expresso _user_ doesn't have to change a thing because since currently we use log4j as the underpinnings, direct use of Log4j would work just as before.
>
>Given this thought, what do you guys think now?  Since I have to switch over all the log4j categories before 5.1 release, I figured now would be the time to switch anyway....
>
>                                        -Mike
>
>
>_______________________________________________
>Opensource mailing list
>Opensource at jcorporate.com
>http://mail.jcorporate.com/mailman/listinfo/opensource
>Archives: http://mail.jcorporate.com/pipermail/opensource/