Groovy Renderer is a component, which can translate a route instance in CamelContext into a route builder in groovy language. By using it, Web Console allows developers disliking prolix XML to edit or update a route using groovy.
Through Web Console, you can review every route in the CamelContext. After opening a route in your browser, the URL may be http://localhost:8080/routes/route1, you can choose the edit link with groovy to update it. A groovy renderer will turn the route into groovy route definition. For example, after chooseing to edit a route defined by the following XML:
The groovy renderer will translate it into a route definition as follows:
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.
Save it and then the route will deliver the following messages by parsing its header.
RenderRoute handles a route at a time. You can use it to revert a route for review or modification.
RenderRoutes can handle a collection of routes at a time. You can obtain the route list from CamelContext and then get a overview of all the route definitions by using renderRoutes method.
Through Web Console, you can view and edit the route. The following page lists all the routes configured in [Camel Context].
Guide for more DSLs
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 DSLs. Groovy renderer can't render every details of the DSLs when opening a route though all of the DSLs can be accepted when creating it. Following is a list showing which DSLs are fully supported and which are not.
You should read the Enterprise Integration Patterns for usage of these DSLs.