-Dlog4j.configuration={file URL} ?
On Dec 28, 8:56 pm, Derek Chen-Becker <[email protected]> wrote:
> That's probably the simplest way to do it. You can also use a system
> property (can't remember off the top of my head) to tell log4j where to get
> its props from, and then just disable Lift's config of log4j by setting
>
> LogBoot.logSetup = () => false
>
> in your bootstrap.
>
> Derek
>
> On Mon, Dec 21, 2009 at 2:54 PM, Mark Feeney <[email protected]> wrote:
> > Hi, all.
>
> > I'm building a web app in Lift 1.0 and deploying to Jetty 6.1.22. I'm
> > trying to figure out the best way (or any way) to externalize the
> > log4j configuration.
>
> > My ideal deployment would look like this:
>
> > /usr/local/jetty/webapps/myapp.war
> > /well/known/location/myapp-log4j.xml (i.e. not in the .war)
>
> > If /well/known/location doesn't exist, a sane log4j.xml (possibly from
> > within the .war) should be used.
>
> > Anyone have advice on how to achieve this? I took a look at
> >http://wiki.liftweb.net/index.php/HowTo_configure_logging, and the
> > default.log4j.xml thing works, but I want config outside the .war.
> > Is overrding LogBoot.defaultProps in Boot.scala -- as mentioned in the
> > linked article -- the answer? (e.g. have it try to return the contents
> > of /well/known/location/myapp-log4j.xml)
>
> > Thanks,
>
> > Mark.
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "Lift" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to
> > [email protected]<liftweb%[email protected]>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/liftweb?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en.
