I've got another (yes, yet another) logging framework planned, and I'd like support for it in commons-logging, but a few questions come up before I write my own wrappers:
1) Is commons-logging still aimed at the 1.1 API? Why? 2) Why don't you allow integral mappings to priorities, instead of calling the actual methods like info(), etc? (My proposed framework has many, many, many more levels, and they're not floodgated like commons-logging uses. In other words, INFO+ERROR is a viable "level".) Without integral mappings, I can make a mapper work, but there's absolutely no way to expose my logger's (proposed!) power to commons-logging without some other invocation mechanism. That may not be a HUGE loss - but considering you could relatively easily support what's there now *and* a non-floodgate model, it's something to consider. ----------------------------------------------- Joseph B. Ottinger [EMAIL PROTECTED] http://enigmastation.com IT Consultant _________________________________________________________________ Join the world�s largest e-mail service with MSN Hotmail. http://www.hotmail.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
