On Aug 12, 2008, at 8:42 AM, Philippe Marschall wrote:
Will Scheidegger wrote:
One thing which puzzles me a bit is the following output in the log
each time the cache module restarts because of changes to the
config I'm doing:
No configuration found. Configuring ehcache from ehcache-
failsafe.xml found in the classpath: jar:file:/ff/tomcat/
fastforward/webapps/magnoliaPublic/WEB-INF/lib/ehcache-1.4.1.jar!/
ehcache-failsafe.xml If for some strange reason magnolia cannot
find the cache configuration, no wonder all my try&error sessions
do not have an effect on the result. Or is that related to
something else?
IMHO yes, my take on this:
It's not Mangolia that is complaining but ehcache about a missing
conifguration file (ehcache.xml). If that troubles you, simply
supply it. It won't change much though because Magnolia configures
ehcache programmatically. See /modules/cache/config/
Correct. On startup, we instance a ehcache Configuration object from /
modules/cache/config/cacheFactory/defaultCacheConfiguration, and set
it as the default in ehcache. By then, ehcache has already tried to
load its configuration from the fs and classpath, which is why you see
this message. Our default configuration should have been bootstrapped,
so if you make any changes under that node, it should be picked up, as
long as it can be mapped to a net.sf.ehcache.config.CacheConfiguration
by content2bean.
Cheers,
-g
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/
----------------------------------------------------------------
