Danny Angus wrote:
>>Almost no application's primary concern is logging. James has exactly the
>>same concern with logging that other server applications, such as
>>Apache and
>>Tomcat, have: the need to record information about the application's
>>operation. Providing an API is not the same as providing a mechanism.
>>Adopting the Jakarta Commons Logging API would be one way to provide a
>>standard contract without specifying the runtime mechanism. But
>>log(String)
>>and log(String, Exception) are insufficient.
>>
>>
>
>And yet Tomcat and the servlet API you quote provide only for log(String)
>leaving any more sophisticated logging requirement to the discretion of
>servlet writers.
>
... and massive headaches for developers attempting to unify things. Leaving
this sort of thing to the discretion of the servlet writers is just plain
bad. I've has spent way to much time wrapping and working around logging
systems because of APIs that havn't considered that tools are deployed
in an
environment where the developer is out of the picture. Logging is more
related to management policies that anything from a developer.
Cheers, Steve.
>
>d.
>
>
>
>
>
>--
>To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
>
>
>
--
Stephen J. McConnell
OSM SARL
digital products for a global economy
mailto:[EMAIL PROTECTED]
http://www.osm.net
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
