On Friday, January 17, 2003, at 11:10 AM, Paul Hammant wrote:
However I am beginning to thing that no reusable bean/comp should log in its own right. Logging+1 .. Much cleaner than sprinkling logging code throughout, and also solves the logkit/log4j/commons-logging issues. And it will end all the questions I get from coworkers about Altrmi's output on STDOUT :)
should be the choice of an /application/ maker. If a reusable bean or reusable comp has issues,
they should be thrown as exceptions. If they have warnings, there should be a monitor/listener
mechanism (if the bean/comp user wants to monitor/listen). If there is info, then the listener is
the same solution.
-pete
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
