> > > A facade is meant to behave > > > roughly the same across toolkits and it is > > > easy enough to make it do so ;) > > > > toString meets those criteria, yes? > > > > Facades should also be faithful about passing on as much information as > they can. For cases where the underlying logging implementation supports
I think "logging" is not a Facade, but an Adapter (if anything). You need a very MODEST FUNCTIONALITY logging. There are a bunch of logging toolkits providing this functionality (and MUCH MORE but you DON'T NEED that much more). You don't want to bind your software to any of these toolkits. >From this point of view it is not interesting that log4j has object and the others string. What is interesting what functionality you want in this modest functionality toolkit and port in the adapter what's needed. Altough I think that whatever your choice was the net output should be more or less the same whichever logkit is faded behind the logging. The user of the logging package (e.g. digester) can't count on the capabilities of log4j in relation with the objects. incze -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
