+1 for doing it in 2.0. Basically , Spring will pick the schema from the jars in the class path. So the change will not effect the camel application if we don't publish them into the web site. But there are some tools such as Eclipse will look up the schema from the target name space.
If we change the target namespace for camel schema , user's old camel spring configuration file need to be updated. I think we'd better not touch 1.x branch to keep the consistence. BTW, we also need to update the script[1] which copies the maven snapshots schema into the web site when we change the target namespace for camel schema. [1]https://svn.apache.org/repos/asf/activemq/scripts/copy_camel_snapshot_xsd.py Willem. Hadrian Zbarcea wrote: > Hi, > > In camel schemas > targetNamespace="http://activemq.apache.org/camel/schema/spring"; > > The location however is at http://camel.apache.org/schema/spring/ (but > still available at the old activemq location. Do you think it would be > a good move to change it now to > targetNamespace="http://camel.apache.org/schema/spring"; > > I personally think we should do it for 2.0, not so sure about the 1.x > branch. > > Thoughts? > > Hadrian >
