paulbrickell wrote:
This is quite painful, but having followed the steps described above eclipse
is now happy that my XML files are valid. But what happens when I deploy my
project?
Hard coded paths are not gonna do it really.
Is there a 'real' solution for this?
Using a catalog *is* the real solution. Spring has its own internal
catalog built from all the META-INF/spring.schemas files it finds on the
classpath that does the same job at runtime that it uses to resolve the
http://cxf.apache.org/schemas/... URIs to Class.getResource locations
(i.e. inside the JAR files).
Ian
--
Ian Roberts | Department of Computer Science
[EMAIL PROTECTED] | University of Sheffield, UK
