Yipee, today i upgraded our Cocoon and it fixes those log messages. However, it causes a problem with the Dispatcher seed-v2 site (samples/index.html busts) so i have not committed it.
If anyone else wants to try it, follow the instructions in etc/cocoon_upgrade/ I needed to keep our fop-*.jar rather than Cocoon's and i needed to tweak our WEB-INF/xconf/forrest-core.xconf for some changes with the "template" block. This latter might be what causes the Dispatcher issue. -David David Crossley (JIRA) wrote: > direct the ehcache log messages to file not stdout, reduce loglevel > ------------------------------------------------------------------- > > Key: FOR-750 > URL: http://issues.apache.org/jira/browse/FOR-750 > Project: Forrest > Type: Bug > Components: Core operations > Versions: 0.8-dev > Reporter: David Crossley > Fix For: 0.8-dev > > > The messages from the Cocoon cache are coming to the stdout console. They > should be going to WEB-INF/logs/ like the rest and should be configurable so > not at DEBUG level by default. > > Other log messages are handled by logkit.xconf file. These ehcache ones > should probably handled by log4j, but our WEB-INF/classes/log4j.properties > seems to have no effect. > > --
