You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by asaksena1 <an...@gmail.com> on 2008/12/18 17:48:13 UTC
Why is ServerRoutes a java file?
For configuring simple Server Routes (if I'm not doing any transformation
etc. using EIP)
e.g.
from("jms:queue:order").to("orderFinder");
Can we not have ServerRoutes and a simple xml configuration file? (or
something similar)
Also, I reckon every time we make a change to ServerRoutes, we have to
bounce the Camel Engine. Is there a way to get around it?
Thanks
-Anurag
--
View this message in context: http://www.nabble.com/Why-is-ServerRoutes-a-java-file--tp21076469s22882p21076469.html
Sent from the Camel - Development mailing list archive at Nabble.com.
Re: Why is ServerRoutes a java file?
Posted by James Strachan <ja...@gmail.com>.
2008/12/18 asaksena1 <an...@gmail.com>:
>
> For configuring simple Server Routes (if I'm not doing any transformation
> etc. using EIP)
> e.g.
> from("jms:queue:order").to("orderFinder");
>
> Can we not have ServerRoutes and a simple xml configuration file? (or
> something similar)
Sure - use whichever you prefer - Java, Scala or XML
> Also, I reckon every time we make a change to ServerRoutes, we have to
> bounce the Camel Engine. Is there a way to get around it?
Deploy your Spring XML document inside the ServiceMix Kernel which
will hot-reload on change to the XML and redeploy your EIP routes
dynamically
http://servicemix.apache.org/SMX4KNL/index.html
We should probably have a tutorial/demo somewhere showing this in action...
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://fusesource.com/