This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new 037a1433195 Regen
037a1433195 is described below
commit 037a14331951a25dd2179fffdbdeb09566d9253c
Author: Claus Ibsen <[email protected]>
AuthorDate: Sat Oct 21 08:46:17 2023 +0200
Regen
---
.../main/java/org/apache/camel/support/DefaultComponent.java | 11 ++++++-----
.../main/java/org/apache/camel/support/DefaultEndpoint.java | 11 ++++++-----
.../apache/camel/support/RestConsumerContextPathMatcher.java | 6 ++++--
3 files changed, 16 insertions(+), 12 deletions(-)
diff --git
a/core/camel-support/src/main/java/org/apache/camel/support/DefaultComponent.java
b/core/camel-support/src/main/java/org/apache/camel/support/DefaultComponent.java
index 3f261b397b2..2599063264f 100644
---
a/core/camel-support/src/main/java/org/apache/camel/support/DefaultComponent.java
+++
b/core/camel-support/src/main/java/org/apache/camel/support/DefaultComponent.java
@@ -232,11 +232,12 @@ public abstract class DefaultComponent extends
ServiceSupport implements Compone
}
/**
- * Allows for bridging the consumer to the Camel routing Error Handler,
which mean any exceptions (if possible) occurred while
- * the Camel consumer is trying to pickup incoming messages, or the likes,
will now be processed as a message and handled by the routing Error Handler.
- * Important: This is only possible if the 3rd party component allows
Camel to be alerted if an exception was thrown. Some components handle this
internally only,
- * and therefore bridgeErrorHandler is not possible. In other situations
we may improve the Camel component to hook into the 3rd party component
- * and make this possible for future releases.
+ * Allows for bridging the consumer to the Camel routing Error Handler,
which mean any exceptions (if possible)
+ * occurred while the Camel consumer is trying to pickup incoming
messages, or the likes, will now be processed as a
+ * message and handled by the routing Error Handler. Important: This is
only possible if the 3rd party component
+ * allows Camel to be alerted if an exception was thrown. Some components
handle this internally only, and therefore
+ * bridgeErrorHandler is not possible. In other situations we may improve
the Camel component to hook into the 3rd
+ * party component and make this possible for future releases.
* <p/>
* By default the consumer will use the
org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be
* logged at WARN/ERROR level and ignored.
diff --git
a/core/camel-support/src/main/java/org/apache/camel/support/DefaultEndpoint.java
b/core/camel-support/src/main/java/org/apache/camel/support/DefaultEndpoint.java
index 4701779a5bd..dda837cc5e2 100644
---
a/core/camel-support/src/main/java/org/apache/camel/support/DefaultEndpoint.java
+++
b/core/camel-support/src/main/java/org/apache/camel/support/DefaultEndpoint.java
@@ -298,11 +298,12 @@ public abstract class DefaultEndpoint extends
ServiceSupport implements Endpoint
}
/**
- * Allows for bridging the consumer to the Camel routing Error Handler,
which mean any exceptions (if possible) occurred while
- * the Camel consumer is trying to pickup incoming messages, or the likes,
will now be processed as a message and handled by the routing Error Handler.
- * Important: This is only possible if the 3rd party component allows
Camel to be alerted if an exception was thrown. Some components handle this
internally only,
- * and therefore bridgeErrorHandler is not possible. In other situations
we may improve the Camel component to hook into the 3rd party component
- * and make this possible for future releases.
+ * Allows for bridging the consumer to the Camel routing Error Handler,
which mean any exceptions (if possible)
+ * occurred while the Camel consumer is trying to pickup incoming
messages, or the likes, will now be processed as a
+ * message and handled by the routing Error Handler. Important: This is
only possible if the 3rd party component
+ * allows Camel to be alerted if an exception was thrown. Some components
handle this internally only, and therefore
+ * bridgeErrorHandler is not possible. In other situations we may improve
the Camel component to hook into the 3rd
+ * party component and make this possible for future releases.
* <p/>
* By default the consumer will use the
org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be
* logged at WARN/ERROR level and ignored.
diff --git
a/core/camel-support/src/main/java/org/apache/camel/support/RestConsumerContextPathMatcher.java
b/core/camel-support/src/main/java/org/apache/camel/support/RestConsumerContextPathMatcher.java
index d8183fad16c..a5d32037997 100644
---
a/core/camel-support/src/main/java/org/apache/camel/support/RestConsumerContextPathMatcher.java
+++
b/core/camel-support/src/main/java/org/apache/camel/support/RestConsumerContextPathMatcher.java
@@ -238,6 +238,7 @@ public final class RestConsumerContextPathMatcher {
/**
* Pre-compiled consumer path for wildcard match
+ *
* @param consumerPath a consumer path
*/
public static void register(String consumerPath) {
@@ -257,6 +258,7 @@ public final class RestConsumerContextPathMatcher {
/**
* if the rest consumer is removed, we also remove pattern cache.
+ *
* @param consumerPath a consumer path
*/
public static void unRegister(String consumerPath) {
@@ -300,9 +302,9 @@ public final class RestConsumerContextPathMatcher {
/**
* Matches the given request path with the configured consumer path
*
- * @param requestPath the request path
+ * @param requestPath the request path
* @param isUriTemplate the consumer path which may use { } tokens
- * @return <tt>true</tt> if matched, <tt>false</tt> otherwise
+ * @return <tt>true</tt> if matched, <tt>false</tt> otherwise
*/
private static boolean matchRestPath(String requestPath, String
consumerPath, boolean isUriTemplate) {
// deal with null parameters
