On 4/3/02 4:49 PM, "Geir Magnusson Jr. " <[EMAIL PROTECTED]> wrote:
>>> And in that framework, can they have their components use the generic >>> commons interface for logging? >> >> No. The biggest difference (and it's important to the Avalon community) is >> that logged messages are "Object" in commons, and "String" in LogKit. That >> kind of trashes the idea of sharing a common interface. However, the CODE >> you write can be "independent" of this. > >Sorry - why do I care if a hypothetical commons generic interface doesn't >jive with the Avalon philosophy? OK, so I have other goals... see more ranting below. > >I mean, this conversation gives me an idea - a LoggingLogging project in >commons that has > >1) the same Log interface as o.a.c.l > >2) the LogUser interface (with michaels change to setFactory()) > >3) an empty Factory impl > >And then optional Factory Impls that use the o.a.c.l package to provide real >impl using log4j or logkit. Other than the "empty Factory Impl", you just described commons logging + your proposed change. > >No philosophy. > >No implied framework. How does a default factory implementation become an entire framework? The "heart" is the Log interface, and that interface isn't tied to the use of the factory. > >Push, pull, slide, jigger, throw, catch, .... With your change, you can "push", or import the factory and "pull". For the rest you'll have to submit a more detailed design proposal :-) > >Just a common interface that people can use for logging... > OK. So, if you have decided that the Avalon equivalent to commons logging is not appropriate, and you believe that what you want is commons logging + new interface, then I have no objection. +1, for what it's worth from me :-) <rant> Hey Avalon - do you hear that??? I STILL WANT YOU TO EXTEND THE commons logging Log interface IN YOUR Logger face, I mean interface! ;-) (sorry, just couldn't resist - it's been a long day). Having "Object message" instead of "String message" parameters may not be ideal from your position, but the BENEFITS FAR OUTWEIGH the concerns. In addition, if you could somehow keep Geir in sync with your push interface, it would be even cooler. </rant> <ras> ******************************************* Richard A. Sitze [EMAIL PROTECTED] CORBA Interoperability & WebServices IBM WebSphere Development -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
