On Thu, 22 Jul 2004, Upayavira wrote: > Vadim Gritsenko wrote: > > > Dave Brondsema wrote: > > > >> On Thu, 15 Jul 2004, Dave Brondsema wrote: > >> > >> > >>> We at Forrest are seeing more JCS log messages than we want. I tried > >>> setting up a log4j.properties file to control it, but that didn't > >>> seem to > >>> work. At any rate, it looks like they're using commons logging now, so > >>> according to > >>> http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=108665505130942&w=2 it > >>> can be controlled with LogKit by cocoon. Could somebody do this? > >>> > >>> > >> > >> Since nobody is eager to do this, could give me some guidance so I > >> can do > >> it myself? What files would I have to edit? How does logkit work in > >> cocon? > >> > > > > If you declare system variable: > > > > org.apache.commons.logging.Log=org.apache.commons.logging.impl.LogKitLogger > > > > commons logging will use LogKit. See web.xml, force-property > > parameter. LogKit is set up by CocoonServlet. > > Are you suggesting setting this property in web.xml? Well, as Forrest > uses the CLI, they won't use a web.xml. >
That works for when we run as a webapp. Thanks. > The CLI way would be to add a property tag into the cli.xconf. Now, this > would be a pretty trivial fix to one Cocoon class. Is this what would be > needed? > Sounds like it to me. Can we try it? -- Dave Brondsema : [EMAIL PROTECTED] http://www.brondsema.net : personal http://www.splike.com : programming http://csx.calvin.edu : student org
