avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stephen McConnell" <mcconn...@apache.org>
Subject RE: DO NOT REPLY [Bug 6489] New: - Allow SARs to use custom log targets & formatters from SAR-INF/lib
Date Mon, 18 Feb 2002 17:02:46 GMT

Peter Royal wrote:
> Sent: Monday, 18 February, 2002 17:50
> To: Avalon Developers List
> Subject: Re: DO NOT REPLY [Bug 6489] New: - Allow SARs to use custom log
> targets & formatters from SAR-INF/lib
> 
> 
> On Friday 15 February 2002 11:06 am, Eung-ju Park wrote:
> > > Currently Phoenix does not allow the use of custom LogKit targets and
> >
> > formatters
> >
> > > that reside in the SAR-INF/lib directory, they must be placed in
> > > PHOENIX_HOME/lib.  If you point me in the general direction 
> of where to
> >
> > look I
> >
> > > can try to patch it.
> >
> > Logging is not a application level servirce. it is a system 
> level service.
> > PHOENIX_HOME/lib is correct place for them.
> 
> What are the portability thoughts on a SAR? I was under the 
> impression that a SAR should be self contained.  If I had an 
> application that had a custom log target to email any fatalError's 
> to the program authors, shouldn't that target be inside the SAR? 
> If not a SAR itself is no longer portable between phoenix installations.

Putting on my "enterprise" hat - my answer would be NO.
I'm responsible for the execution of a suite of applications and the 
configuration I declare for logging flows down to each application. I 
know that my "enterprise" policy takes precedence.  If a SAR wants to 
email a log report, then that a feature of the SAR - its not something 
that should interfere with my "enterprise" policy.

My 0.02 euro!

Cheers, Steve.


--
To unsubscribe, e-mail:   <mailto:avalon-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:avalon-dev-help@jakarta.apache.org>


Mime
View raw message