You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@avalon.apache.org by si...@avalon.apache.org on 2004/05/12 16:45:31 UTC
[Apache Avalon Wiki] Updated: AvalonNoLogging
Date: 2004-05-12T07:45:31
Editor: 80.238.41.184 <>
Wiki: Apache Avalon Wiki
Page: AvalonNoLogging
URL: http://wiki.apache.org/avalon/AvalonNoLogging
no comment
Change Log:
------------------------------------------------------------------------------
@@ -99,7 +99,7 @@
In particular, it assumes that there is a '''human''' that find your information '''relevant'''.
-== Callbacks Solve This ==
+=== Callbacks Solve This ===
Instead, we believe that callbacks should be used when you want maximum portability. Use of callbacks enable you to:
@@ -114,3 +114,8 @@
* It enables a reusable component to communicate with the code it is embedded in in a standard Java way. With logging, you have to parse the log files for the same effect. This is a requirement for embeddable components. If a component lacks features for integration with the container, it is a much worse component than one that has such features.
In short - '''this solution gives maximum flexibility, maximum embeddability, for no cost.'''
+
+---- Comment by Ceki Gülcü ----
+
+I am intrigued by your article. Would it be possible to show an
+example of what you have in mind with sample code? Thanking you in advance.
---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@avalon.apache.org
For additional commands, e-mail: cvs-help@avalon.apache.org