Page History

...

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
 <route id="route1" xmlns:ns2="http://camel.apache.org/schema/web" xmlns="http://camel.apache.org/schema/spring">
     <description>This is an example route which you can start, stop and modify</description>
     <from uri="seda:foo"/>
     <to uri="mock:results" id="to1"/>
 </route>

The groovy renderer will translate it into a route definition as follows:

import org.apache.camel.language.groovy.GroovyRouteBuilder;
 class GroovyRoute extends GroovyRouteBuilder {
     void configure() {
         from("seda:foo").to("mock:results")
     }
 }

Then you can update the route by input DSLs into the configure method. For example, you can change it into a Content Based Router by updating it as follows.

class GroovyRoute extends GroovyRouteBuilder {
     void configure() {
         from("seda:a").choice().when(header("foo").isEqualTo("bar")).to("seda:b")  
            .when(header("foo").isEqualTo("cheese")).to("seda:c").otherwise().to("seda:d")
     }
 }

Save it and then the route will deliver the following messages by parsing its header.

...

Though all of the DSLs can be accepted to create routes, but groovy renderer can't render every details of the routes when opening them. Web Console focuses on providing a editor for developers to update a route at runtime, but won't try to provide a development environment with full support of DSL. Following is a list showing which DSLs are fully supported and which can't be.

Supported DSLs

...

• aggregate

...

• choice

...

• convertBody

...

• deadLetter

...

• delay

...

• enrich

...

• filter

...

• from

...

• loadBalance

...

• loop

...

• marshal

...

• pipeline

...

• recipientList

...

• routeSlip

...

• setBody

...

• sort

...

• throttle

...

• to

...

• transform

...

• wireTap

...

• xPath

Un-supported DSLs

...

• bean

...

• process