Torsten Curdt wrote:
David Crossley wrote:
The original problem still remains. How does Cocoon
manage to get logkit to handle the ehcache messages,
whereas with Forrest they come to the console?
IIRC the integration with JCL was broken and Sylvain
fixed it in trunk.
Thanks, that did the
That certainly does help to explain the difference
in log-levels. Thanks Carsten.
Someone should document that :-)
The original problem still remains. How does Cocoon
manage to get logkit to handle the ehcache messages,
whereas with Forrest they come to the console?
IIRC the integration with
Cocoon 2.2 uses running modes for resolving properties. In the
WEB-INF/properties directory, you'll find two modesprod and dev. By
default, 2.2 is running in dev mode which overrides all log levels
defined in the logkit config and sets them to DEBUG.
You can either set the running mode to prod by
Carsten Ziegeler wrote:
Cocoon 2.2 uses running modes for resolving properties. In the
WEB-INF/properties directory, you'll find two modesprod and dev. By
default, 2.2 is running in dev mode which overrides all log levels
defined in the logkit config and sets them to DEBUG.
You can either
Can anyone explain the following difference ...
Doing 'cocoon.sh' with 2.2 trunk at my local working copy,
with all default blocks. The logfile is filling up with
EHCache debug messages into the logfile at
build/webapp/WEB-INF/logs/cocoon.log
At cocoon.zones.apache.org i cannot find any mention
As you know, at Apache Forrest we use Cocoon 2.2 trunk.
A few months ago we upgraded our packaged Cocoon.
Now we get messages from EHCache coming to stdout
when we use our Jetty demo webapp.
Of course tweaking WEB-INF/logkit.xconf has no effect
because they are coming to the console.
However,
