Thanks Jared for your quick reply, it seems that naming the root element in the ehcache.xml doesn't avoid the core problem (same-ish exception: org.apache.shiro.cache.CacheException: net.sf.ehcache.CacheException: Another CacheManager with same name 'shiro' already exists in the same VM...)
...so I think I'll take your second suggestion and just implement my own factory class that will enforce a singleton instantiation. Thank you again. -- View this message in context: http://shiro-user.582556.n2.nabble.com/EhCache-initialization-exception-Another-unnamed-CacheManager-already-exists-in-the-same-VM-tp7577532p7577534.html Sent from the Shiro User mailing list archive at Nabble.com.
