+1 on 2.0 only I assume we can still publish 1.x schemas to the old activemq location at Apache for as Willem said to keep Eclipse and IDEA etc. that can fetch these schemas into the editor for code completion in the XML.
When we do the change on 2.0 we must remember there are several spring schema files in the src folder we need to update (camel-spring, camel-cxf and maybe some others) And should we on 2.0 remove the older schema entries for all the Camel 1.x releases? On Fri, Jan 23, 2009 at 4:48 PM, Hadrian Zbarcea <hzbar...@gmail.com> wrote: > @Willem, I am working on a set of camel scripts. > Thanks > Hadrian > > On Jan 23, 2009, at 10:29 AM, Willem Jiang wrote: > >> +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 >>> >> > > -- Claus Ibsen Apache Camel Committer Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/
