The Apache Jenkins build system has built Camel.trunk.notest (build #2750)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2750/
to view the results.
Yeah, I agree Claus.
That's why I'm not a big fan of my proposed solution, It would be cleaner
if the CamelContext (or CamelContextFactoryBean) itself resolved
PropertyPlaceHolder on its own without regarding the implementation
(spring, blueprint, cdi, whatever).
Regards,
On Fri, May 13, 2016 at
Yep, Handler was added just as placeholder as you know, naming is hard :-)
Unless we want to use it also in bean binding, I think a new
annotation would be better to avoid confusion so I'd vote for
@InvokeOnHeader
---
Luca Burgazzoli
On Fri, May 13, 2016 at 2:08 PM, Claus Ibsen wrote:
> Hi
>
> Y
Hi
Yeah that can help with those kind of components. You may want to use
a different name than @Handler as there is a @Handler already in
org.apache.camel for bean binding.
maybe @SwitchByHeader (if people really think of the java switch
statement) or @InvokeFromHeader, @InvokeOnHeader or somethi
