+1 for 2.0.
We might as well keep all the old schemas around though - they do no
harm being around.
2009/1/24 Claus Ibsen :
> +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 th
+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 sche
@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 i
+1 for 2.0 only.
On Fri, Jan 23, 2009 at 11:59 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 tool
+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 chang
+1 to do it.
+1 to do it for 2.0
On Sat, Jan 24, 2009 at 01:54, 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
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://came
