You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@avalon.apache.org by bu...@apache.org on 2002/05/28 07:42:51 UTC

DO NOT REPLY [Bug 9444] - Back Compatibility Fix for AbstractLogEnabled

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

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9444

Back Compatibility Fix for AbstractLogEnabled

jeremias.maerki@outline.ch changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME



------- Additional Comments From jeremias.maerki@outline.ch  2002-05-28 05:42 -------
You might want to download FOP from the CVS (tag fop-0_20_2-maintain) or wait a 
week or two for the next release. FOP has been updated to use Avalon's Logger 
interface. The website already reflects this change.

I guess you're working with ECM. You could also write a little Avalon wrapper 
around FOP that extends from AbstractLoggable. Then you get that wrapper via 
the ComponentManager, so ECM will give you a Logkit Logger instead of an Avalon 
Logger.

I hope this helps.

Jeremias Maerki, FOP committer

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>