spring-tool-3.0.xsd not found when using spring 2.x

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a Spring 2.x and ehcache-spring-annotations 1.1 project
2. Exclude ehcache-spring-annotations Spring 3 dependencies (because you're 
using Spring 2.x)

What is the expected output? What do you see instead?
At deployment time, a warning is shown.  It appears that your xsd points to 
spring-tools-3.0.xsd which of course is not available.
org.xml.sax.SAXParseException: schema_reference.4: Failed to read schema 
document 'http://www.springframework.org/schema/tool/spring-tool-3.0.xsd', 
because 1) could not find the document; 2) the document could not be read; 3) 
the root element of the document is not <xsd:schema>.

What version of the product are you using? On what operating system?
Spring 2.x and ehcache-spring-annotations 1.1, Windows XP Prof

Please provide any additional information below.
So, I realize that this is not a true bug. Is there a work around available for 
Spring 2.x users?

Original issue reported on code.google.com by timmy.st...@gmail.com on 6 Jul 2010 at 1:02

[GoogleCodeExporter]

Forgot to mention this, but as a side effect, the referenced CacheManager name 
is not looked up. E.g.: <ehcache:annotation-driven cache-manager="myManager" /> 
will still search for cacheManager instead of myManager bean.

The following is a snippet from the 1.1 xsd file:
<tool:annotation kind="ref">
    <tool:expected-type type="net.sf.ehcache.CacheManager"/>
</tool:annotation>
These elements are also available in the spring-tool-2.0.xsd and 
spring-tool-2.5.xsd files. Is it really necessary to use the 3.0 xsd file?

Original comment by timmy.st...@gmail.com on 6 Jul 2010 at 2:23

[GoogleCodeExporter]

Thanks for the report. We'll switch to the 2.5 xsd and get a 1.1.2 release out 
soon.

Original comment by eric.dalquist on 6 Jul 2010 at 3:14

• Changed state: Accepted
• Added labels: Milestone-Release1.1.2, Milestone-Release1.2.0

[GoogleCodeExporter]

Original comment by eric.dalquist on 6 Jul 2010 at 3:27

• Changed state: Fixed

[GoogleCodeExporter]

Thanks a lot for the quick release! As expected, the stacktrace is gone at 
deployment time.

Original comment by timmy.st...@gmail.com on 7 Jul 2010 at 6:48

[GoogleCodeExporter]

Great, thanks for the verification as well.

Original comment by eric.dalquist on 7 Jul 2010 at 1:45