Page History

...

Unsupported Features List

...

Creating New Classes

When writing a route in Java DSL, we often create new classes. For example, we may create a processor as follows:

...

• happen to: aggregate, bean, process, etc.
• alternative solution: you should build the processors externally, register them on Camel Context and then you can use them by using beanRef or processRef DSL. For such an example, you should refer Content Based Routing on Camel.

...

Invoking Un-Imported Classse

This feature also appears frequently. In the try...catch DSL or onException DSL, we may use some external or custom exception classes. But current groovy renderer doesn't process the import packages, so you should manually add the import lines each time you edit it. Another problem is that groovy renderer can't return the instance name of that class. For example, you may define a route like:

...

However, groovy renderer can only render the first filter because a closure is unreadable in Camel Context.

...

Other Features

Some expression and predicate have complex and refractory toString method, so the ExpressionRenderer and PredicateRenderer class written are implemented a little hard.