This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/camel.git
commit a3539d95533728fac60fb2d947a42c5c946710cf Author: Claus Ibsen <[email protected]> AuthorDate: Mon Sep 2 10:38:09 2019 +0200 CAMEL-13917: Configuring endpoints with consumer. prefix for consumer options is no longer supported as they should be regular options instead. This also avoid reflection setting properties. --- MIGRATION.md | 4 ++++ .../org/apache/camel/blueprint/handler/CamelNamespaceHandler.java | 3 --- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/MIGRATION.md b/MIGRATION.md index 680b032..1fa1eb4 100644 --- a/MIGRATION.md +++ b/MIGRATION.md @@ -139,6 +139,10 @@ The `rxjava2` component has been renamed to `rxjava`, and it's corresponding com We have also renamed `camel-jetty9` to `camel-jetty`. The supported scheme is now `jetty`. +### Using endpoint options with consumer. prefix + +Endpoints with `consumer.` prefix such as `consumer.delay=5000` are no longer supported (deprecated in latest Camel 2.x) and you should just use the option without the `consumer.` prefix, eg `delay=5000`. + ### Tracing A new tracer has been implemented and the old tracer has been removed. diff --git a/components/camel-blueprint/src/main/java/org/apache/camel/blueprint/handler/CamelNamespaceHandler.java b/components/camel-blueprint/src/main/java/org/apache/camel/blueprint/handler/CamelNamespaceHandler.java index 4a6e4c6..c241ffd 100644 --- a/components/camel-blueprint/src/main/java/org/apache/camel/blueprint/handler/CamelNamespaceHandler.java +++ b/components/camel-blueprint/src/main/java/org/apache/camel/blueprint/handler/CamelNamespaceHandler.java @@ -1216,9 +1216,6 @@ public class CamelNamespaceHandler implements NamespaceHandler { URI u = new URI(uri); Map<String, Object> parameters = URISupport.parseParameters(u); Object value = parameters.get("scheduler"); - if (value == null) { - value = parameters.get("consumer.scheduler"); - } if (value != null) { // the scheduler can be quartz or spring based, so add reference to camel component // from these components os blueprint knows about the requirement
