DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28044>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=28044

Patch, Avalon Logging to Commons Logging Conversion.





------- Additional Comments From [EMAIL PROTECTED]  2004-03-30 22:14 -------
[Jeremias]

Yes, this work definitely needs optimization--what you mention is a major area 
(Axis does exactly as you say over and over again.)--I just did a straight 
conversion first (several hours of work).  I'm not a logging expert--I just 
need a foothold for the conversion that can *then* be optimized.  If right now 
as you say, we're just the same as Avalon, I'm quite thrilled that I could even 
manage that.  The changes you are suggesting can happen next.    

BTW, would you already know how to make these changes quickly, after I commit 
the patch?  If you can zoom through this in 20-30 minutes, that would save me a 
lot of time.  Else I'll research it.  


[Chris]

<Q>
I think this is the logger for Batik in the Transcoder. If we dont set it, does 
this mean there is no way of seeing warnings from Batik processing?
</Q>

Well, Batik doesn't use Avalon.  It was the logger for the Avalon ContainerUtil 
(whether the latter is currently activated, I didn't research), which in turn 
can't accept a Commons-Logger.  If we need to, we can give it an Avalon 
ConsoleLogger instead.  Or, switch to a Container that will allow us to use 
Commons-Logging.  Or, not use a container at all (I don't know what 
a "container" here does for us anyway.)  Or, switch to System.err.println() a 
la Batik and Xalan.  I don't care much here.  (Perhaps even ContainerUtil can 
be subclassed to take a Commons Logging object?)  Comments welcome--but we 
should probably get this working as well.

Glen

Reply via email to