Great solution for choosing what processor to call on the basis of the value
of a specific header.
I will use this for this solution.
I also have another problem in the redis solution.
In the class CommandDispatcher a lot of "getters" on different headers or
sometimes the same header are defined.
You may also have a look at HeaderSelectorProducer which let you to
use annotations and/or lambdas as callbacks for a given header i.e. :
https://github.com/apache/camel/blob/master/components/camel-consul/src/main/java/org/apache/camel/component/consul/enpoint/ConsulAgentProducer.java
https://gi
Hi arno,
With modern javac and JVMs I don't think there will be any performance
or footprint impact from having one or more classes.
Apart from CC, consider also whether the code will be easier to
understand/maintain and extend. If you belive it will be bettter, then
go for it.
we at Camel comm
