As recommended in our Documentation, it is a good practice to specify the version for XSD used by Camel Spring Projects when editing the Route. For example:

xsi:schemaLocation=" http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring-2.23.2.xsd"

Without setting the version 2.x.x, validation errors might arise when editing the Routes as the XSD for Camel 3 will be used.

At runtime, however, Fuse will try to find the camel-spring-2.23.2.xsd from the JAR file (f.e. camel-spring-2.23.2.fuse-780036-redhat-00001.jar)

The problem is that the JAR file includes a file with a different name: camel-spring-v2.23.xsd (Notice the "v") so it won't be found.

Within our documentation it is recommended "Change back to the default, camel-spring.xsd, when you are finished editing. ". This implies you change back and forth the XSD each time you edit your Route. That's not a very scalable approach.

Is it possible to rename as camel-spring-2.XX.X.xsd in our camel-spring JAR file so that both the Editor and the Runtime will use the same XSD?