On Sat, 16 Feb 2002, B.Gorkem ERCAN wrote:
> Date: Sat, 16 Feb 2002 01:16:02 +0200
> From: B.Gorkem ERCAN <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Logging mess
>
> Hi,
> On my daytime job I have to manage several J2EE applications
> developed by several development teams. Recently our administrator
> complained that these applications all use different logging mechanisms
> which is creating a mess :). In order to avoid I have decided to advise
> on the use of just one common loggin API. I am going to to use
> commons-logging but I want to add the possibility to control the logging
> behaviour of all the applications running on the same JVM so that I can
> set some of the logging properties on individual applications centrally.
> What I have in mind is to have a LoggingManager structure somehow like
> the SecurityManager. I want to be able to code in some of the
> properties so that they are not easilly changeable but in the mean time
> allow easy to edit cofiguration files on other properties. Do you think
> this is a right approach? Is it interesting to have these in the
> commons-logging?
>
Well, you might want to join in the discussions on the design of the
commons logging API, which is happening on the COMMONS-DEV mailing list.
The current code (thanks to some updates from Costin) allows you to
install commons-logging.jar in a shared repository (like the "lib"
directory in Tomcat), but still allow each webapp to define their own
logging configuration if you want to (they would default to the global
settings). Alternatively, you could put a copy in each webapp, and they
would be totally insulated.
Since you can accomplish any reasonable combination already, I don't
personally see any need to make commons-logging any more complicated --
it's *only* purpose in life is to allow you to write your application
components to a single API, and then make a choice at deployment time on
which logging technology will actually be used underneath.
> Thanks
> B. Gorkem ERCAN
>
Craig
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
