I really hope that is NOT they way to do it. That significantly complicates things.
One of the reasons we choose SY is that it is built on Camel, which gives us access to many integration components, and is easy to work with.
If this is the case it will require additional server tweaking and deploying.
The camel-mvel jar is already included in the distribution and is available as an expression language in Camel:
It looks like MVEL component support was added in 2.12:
The current version of Camel used in SY is 2.10, so that explains the resolution failure of the mvel endpoint in your route.
I am using this version of camel mvel - http://mvnrepository.com/artifact/org.apache.camel/camel-mvel/2.10.0
Keith, I am looking at Camel URI - SwitchYard - Project Documentation Editor and it seems that, where I would usually write
<routes xmlns="http://camel.apache.org/schema/spring"> <!-- here we define the bar route --> <route id="bar"> <from uri="direct:bar"/> <to uri="mvel:bar"/> </route> <!-- we could add more routes if we like, but in this example we stick to one route only --> </routes>
and be able to edit this in the full glory of the fuse camel editor, that I would have to use special SY xml syntax?
So, I can only use camel routing if I route from SY service to SY service, and can use existing camel routing logic, but not any the camel components in the usual camel routing - xml or java?
If I want to, in my case, use mvel, then I have to do some extra SY specific steps, using SY xml?
MVEL as a component won't be available until Camel 2.12. There is no hard restriction on which endpoints you use in Camel routes deployed in SwitchYard. You can definitely use things like direct://, seda://, xslt://, etc. to coordinate between routes inside a given service (we allow multiple routes in a single Java DSL RouteBuilder or XML <routes> definition). In theory, you could also invoke an outside endpoint (e.g. jms://) in this manner as well, but we recommend against that in general practice.
Since camel-mvel is already included with SwitchYard, the only real requirement to use an MVEL endpoint in your route is to upgrade all the Camel modules from 2.10 to 2.12.