I had a similar problem with Springmodules' Lucene integration...
I'm running Eclipse 3.4.1 (J2EE) with SpringIDE installed.
My project is a WebProject deployed onto a Apache Tomcat 6, running on JDK 6.
I have the (complete) spring.jar (v-2.5.6) + spring-modules-lucene.jar (v-0.9) in my classpath.
I registered the spring-lucene.xsd at my Eclipse /XML/XML Catalog as I *thought* it should look like:

I referenced the spring-lucene schema like:
Code:
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:lucene="http://www.springmodules.org/schema/lucene"
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
http://www.springmodules.org/schema/lucene
http://www.springmodules.org/schema/lucene/spring-lucene.xsd
">
...
</beans>
When I tried to start my Tomcat, I got the following error(s):
Code:
2009-01-15 11:15:20,067 (FrameworkServlet.java:290) - Context initialization failed
org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Failed to import bean definitions from relative location [conf/AuditDispatcher.xml]
Offending resource: ServletContext resource [/WEB-INF/SpringDispatcher-servlet.xml];
nested exception is org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 8 in XML document from ServletContext resource [/WEB-INF/conf/AuditDispatcher.xml] is invalid;
nested exception is org.xml.sax.SAXParseException: The element type "META" must be terminated by the matching end-tag "</META>".
at org.springframework.beans.factory.parsing.FailFastProblemReporter.error(FailFastProblemReporter.java:68)
at org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:85)
at org.springframework.beans.factory.parsing.ReaderContext.error(ReaderContext.java:76)
[...]
A little research lead me to this thread, which did not really help me a lot...
Some more research led me to spring-modules-lucene.jar!/META-INF/spring.schemas.
Code:
http://www.springmodules.org/schema/lucene/lucene-index.xsd=org/springmodules/lucene/index/config/spring-lucene.xsd
There I found that the springmodules schema location differs from what I *thought* it would look like...
Instead of http://www.springmodules.org/schema/lucene/spring-lucene.xsd (as you might expect due to the schema file name...)
it was http://www.springmodules.org/schema/lucene/lucene-index.xsd.
After I changed my XML Catalog entry...

... and the schema import within my Spring configuration ...
Code:
<beans xmlns="http://www.springframework.org/schema/beans"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:lucene="http://www.springmodules.org/schema/lucene"
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
http://www.springmodules.org/schema/lucene
http://www.springmodules.org/schema/lucene/lucene-index.xsd
">
...
</beans>
... everything worked like a charm.
A little note: perhaps you have noticed that my XML Catalog / location entry differs a little from what you generally see on the net...
Instead of jar:file:/... I'm referencing the schema file with jar:platform:/resource/.../some.jar!/path/to/schema.xsd.
This way I don't have to use an absolute, but an workspace relative file path.
I needed to do this, because I'm carrying my workspace around on a portable disk...
So far,
hope this helps some of you