On Monday 18 February 2002 12:02 pm, Stephen McConnell wrote: > > 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.
Perhaps the emailing of logs is a bad example (it was completely contrived, that's not why I have custom targes, I have copied the Cocoon formatter that display just the classname from the procedure that did the logging, and thus I need my own custom targets to use the custom formatter). But if it is deemed that custom log targets need to go in PHOENIX_HOME/lib, thats fine, since we responsible for the phoneix installation as well as our SAR. The majority of our customers don't have an admin such as you :) -pete -- peter royal -> [EMAIL PROTECTED] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
