--
You received this message because you are subscribed to the Google Groups "ehcache-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ehcache-user...@googlegroups.com.
To post to this group, send email to ehcach...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ehcache-users/e5ff60e5-32a7-4047-b243-8c21834c0b04%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
At a first glance it looks like you need to provide a namespace prefix for the <none> elements. You might also find it more convenient to define “http://www.ehcache.org/v3” as the default namespace. The exception one deeper in the chain should be pointing you at that.
Chris
To unsubscribe from this group and stop receiving emails from it, send an email to ehcach...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to ehcache-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ehcache-users/c6c47ef6-906b-48c1-97c3-9d824d1de711%40googlegroups.com.
With the attribute xmlns=“http://www.ehcache.org/v3” like you did in your first config. Incidentally the problem with the first configuration is different. The 107 schema and the main schema are both typing their name attributes (of the jsr107:cache and cache-template:cache elements respectively) as xs:ID. Unfortunately this means you can’t have a template with the same name as a 107 defined cache. This is probably fixable in a future release, but for now you’ll need to define non-colliding names.Chris
To unsubscribe from this group and stop receiving emails from it, send an email to ehcach...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to ehcache-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ehcache-users/dd8feb96-87fd-49b1-a25b-c23bfce66fd8%40googlegroups.com.
In order for you to figure out whats going on you need to get the message (and stack trace) of the cause of the XmlConfigurationException… without that and given that the XML is valid in principle it’s impossible to say what is going wrong.
Chris
To unsubscribe from this group and stop receiving emails from it, send an email to ehcach...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to ehcache-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ehcache-users/6bb25aad-a02b-4491-bcd3-d34f832a749e%40googlegroups.com.
The root exception here is: java.io.FileNotFoundException: Documents/my-workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/my-web/WEB-INF/classes/ehcache.xml (No such file or directory)That doesn’t seem to line up correctly with the spring configuration you inlined below.My gut instinct at this point is that there isn’t anything wrong with Ehcache, but that this is a Spring configuration issue. I would double check all your spring configuration and setup, and then try and pursue this through the Spring community channels. In particular I’m doubtful that the spring configuration your quoting is the one being picked up by Spring.
Chris
ParallelWebappClassLoader as the second parameter. I am not sure if it explains anything but wanted to update this thread.