[GitHub] [camel-quarkus] jamesnetherton opened a new pull request #510: chore: Fix pom sorting script execution
jamesnetherton opened a new pull request #510: chore: Fix pom sorting script execution URL: https://github.com/apache/camel-quarkus/pull/510 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [camel-quarkus] davsclaus commented on issue #509: Do not use hard coded ports in integration-tests
davsclaus commented on issue #509: Do not use hard coded ports in integration-tests URL: https://github.com/apache/camel-quarkus/pull/509#issuecomment-561993056 ok to test This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[camel] branch master updated: Regen
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 The following commit(s) were added to refs/heads/master by this push: new 0ec60e6 Regen 0ec60e6 is described below commit 0ec60e6d6e5275b976c96a1e395894f309887f34 Author: Claus Ibsen AuthorDate: Thu Dec 5 05:26:59 2019 +0100 Regen --- components/camel-netty-http/src/main/docs/netty-http-component.adoc | 2 +- components/camel-netty/src/main/docs/netty-component.adoc | 2 +- docs/components/modules/ROOT/pages/netty-component.adoc | 2 +- docs/components/modules/ROOT/pages/netty-http-component.adoc| 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/components/camel-netty-http/src/main/docs/netty-http-component.adoc b/components/camel-netty-http/src/main/docs/netty-http-component.adoc index 30a5ee5..1a8237f 100644 --- a/components/camel-netty-http/src/main/docs/netty-http-component.adoc +++ b/components/camel-netty-http/src/main/docs/netty-http-component.adoc @@ -280,7 +280,7 @@ The component supports 36 options, which are listed below. | *camel.component.netty-http.executor-service* | To use the given EventExecutorGroup. The option is a io.netty.util.concurrent.EventExecutorGroup type. | | String | *camel.component.netty-http.header-filter-strategy* | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter headers. The option is a org.apache.camel.spi.HeaderFilterStrategy type. | | String | *camel.component.netty-http.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed [...] -| *camel.component.netty-http.maximum-pool-size* | The thread pool size for the EventExecutorGroup if its in use. The default value is 16. | 16 | Integer +| *camel.component.netty-http.maximum-pool-size* | Sets a maximum thread pool size for the netty consumer ordered thread pool. The default size is 2 x cpu core 1. Setting this value to eg 10 will then use 10 threads unless 2 x cpu core 1 is a higher value, which then will override and be used. For example if there are 8 cores, then the consumer thread pool will be 17. This thread pool is used to route messages received from Netty by Camel. We use a separate thread pool to ensure ordering [...] | *camel.component.netty-http.netty-http-binding* | To use a custom org.apache.camel.component.netty.http.NettyHttpBinding for binding to/from Netty and Camel Message API. The option is a org.apache.camel.component.netty.http.NettyHttpBinding type. | | String | *camel.component.netty-http.security-configuration.authenticate* | Whether to enable authentication This is by default enabled. | | Boolean | *camel.component.netty-http.security-configuration.constraint* | The supported restricted. Currently only Basic is supported. | | String diff --git a/components/camel-netty/src/main/docs/netty-component.adoc b/components/camel-netty/src/main/docs/netty-component.adoc index 81ef113..92ad922 100644 --- a/components/camel-netty/src/main/docs/netty-component.adoc +++ b/components/camel-netty/src/main/docs/netty-component.adoc @@ -269,7 +269,7 @@ The component supports 80 options, which are listed below. | *camel.component.netty.enabled* | Whether to enable auto configuration of the netty component. This is enabled by default. | | Boolean | *camel.component.netty.executor-service* | To use the given EventExecutorGroup. The option is a io.netty.util.concurrent.EventExecutorGroup type. | | String | *camel.component.netty.lazy-start-producer* | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then [...] -| *camel.component.netty.maximum-pool-size* | The thread pool size for the EventExecutorGroup if its in use. The default value is 16. | 16 | Integer +| *camel.component.netty.maximum-pool-size* | Sets a maximum thread pool size for the netty consumer ordered thread pool. The default size is 2 x cpu core 1. Setting this value to eg 10 will then use 10 threads unless 2 x cpu core 1 is a higher value, which then will override and be used. For example if there are 8 cores, then the consumer thread pool will be 17. This
[GitHub] [camel-quarkus] ppalaga commented on a change in pull request #509: Do not use hard coded ports in integration-tests
ppalaga commented on a change in pull request #509: Do not use hard coded ports
in integration-tests
URL: https://github.com/apache/camel-quarkus/pull/509#discussion_r353962422
##
File path:
integration-tests/support/test-support/src/main/java/org/apache/camel/quarkus/test/AvailablePortFinder.java
##
@@ -0,0 +1,83 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.camel.quarkus.test;
+
+import java.io.IOException;
+import java.net.InetAddress;
+import java.net.InetSocketAddress;
+import java.net.ServerSocket;
+import java.util.HashMap;
+import java.util.Map;
+import java.util.function.Function;
+
+import org.slf4j.Logger;
+import org.slf4j.LoggerFactory;
+
+/**
+ * Finds currently available server ports.
+ */
+public final class AvailablePortFinder {
+private static final Logger LOGGER =
LoggerFactory.getLogger(AvailablePortFinder.class);
+
+/**
+ * Creates a new instance.
+ */
+private AvailablePortFinder() {
+// Do nothing
+}
+
+/**
+ * Gets the next available port.
+ *
+ * @throws IllegalStateException if there are no ports available
+ * @return the available port
+ */
+public static int getNextAvailable() {
+try (ServerSocket ss = new ServerSocket()) {
+ss.setReuseAddress(true);
+ss.bind(new InetSocketAddress((InetAddress) null, 0), 1);
Review comment:
Is this a solution proven to work in practice? Asking because I assume (I
have not looked into the impl) that ServerSocket.bind() does not do any fancy
locking, and therefore two racing threads or processes may get the same port
number as available. But that's perhaps rather unlikely for real world
scenarios and there is enough evidence that this works in practice?
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] [camel-quarkus] asf-ci commented on issue #509: Do not use hard coded ports in integration-tests
asf-ci commented on issue #509: Do not use hard coded ports in integration-tests URL: https://github.com/apache/camel-quarkus/pull/509#issuecomment-561776234 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/camel-quarkus-pr/468/Build result: FAILURE[...truncated 2.02 MB...]Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:77)Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2681) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:3156) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:862) at java.io.ObjectInputStream.(ObjectInputStream.java:358) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:49) at hudson.remoting.Command.readFrom(Command.java:140) at hudson.remoting.Command.readFrom(Command.java:126) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:36) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)ERROR: H48 is offline; cannot locate JDK 1.8 (latest)ERROR: H48 is offline; cannot locate Maven 3.6.2ERROR: H48 is offline; cannot locate JDK 1.8 (latest)ERROR: H48 is offline; cannot locate Maven 3.6.2Adding one-line test results to commit status...ERROR: H48 is offline; cannot locate JDK 1.8 (latest)ERROR: H48 is offline; cannot locate Maven 3.6.2ERROR: H48 is offline; cannot locate JDK 1.8 (latest)ERROR: H48 is offline; cannot locate Maven 3.6.2Setting status of 526640f42086331261c286952a55199b17731a04 to FAILURE with url https://builds.apache.org/job/camel-quarkus-pr/468/ and message: 'FAILURE 223 tests run, 3 skipped, 0 failed.'Using context: default This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[camel] branch master updated (badf907 -> 9ef1c8e)
This is an automated email from the ASF dual-hosted git repository.
janbednar pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git.
from badf907 Regen
add 9ef1c8e Add FAQ entry how to create runnable JAR
No new revisions were added by this update.
Summary of changes:
docs/user-manual/modules/ROOT/pages/faq.adoc | 2 +-
...table-jar.adoc => how-to-create-executable-jar-camel-main.adoc} | 7 +--
2 files changed, 6 insertions(+), 3 deletions(-)
rename
docs/user-manual/modules/ROOT/pages/faq/{how-to-create-executable-jar.adoc =>
how-to-create-executable-jar-camel-main.adoc} (73%)
[GitHub] [camel-k] nicolaferraro opened a new issue #1119: Knative event endpoints may be bidirectional
nicolaferraro opened a new issue #1119: Knative event endpoints may be bidirectional URL: https://github.com/apache/camel-k/issues/1119 When replying to an event with another event, the event should be sent again to the broker (to be verified). If this is correct, we should make sure to do appropriate conversions to cloudevents at knative endpoint level. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[camel-website] 01/01: Some hack to put Camel 3 is here on front page.
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch here
in repository https://gitbox.apache.org/repos/asf/camel-website.git
commit 5ad0440267aa792ac011415b26f4860336605a3f
Author: Claus Ibsen
AuthorDate: Wed Dec 4 17:54:34 2019 +0100
Some hack to put Camel 3 is here on front page.
---
layouts/index.html | 3 +++
1 file changed, 3 insertions(+)
diff --git a/layouts/index.html b/layouts/index.html
index b99d9c3..0e5dc18 100644
--- a/layouts/index.html
+++ b/layouts/index.html
@@ -12,6 +12,9 @@
Camel is an open source integration framework that empowers
you to quickly and easily integrate various systems consuming or producing data.
Get
started
+ Apache Camel 3.0 is here
+
+ What's New
{{ .Content }}
[camel-website] branch here created (now 5ad0440)
This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a change to branch here in repository https://gitbox.apache.org/repos/asf/camel-website.git. at 5ad0440 Some hack to put Camel 3 is here on front page. This branch includes the following new commits: new 5ad0440 Some hack to put Camel 3 is here on front page. The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference.
[camel] branch master updated: Regen
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 The following commit(s) were added to refs/heads/master by this push: new badf907 Regen badf907 is described below commit badf907a09e05eafa3b2100ff3e49dffd07111b0 Author: Claus Ibsen AuthorDate: Wed Dec 4 15:00:01 2019 +0100 Regen --- docs/components/modules/ROOT/pages/netty-component.adoc | 4 ++-- docs/components/modules/ROOT/pages/netty-http-component.adoc | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/components/modules/ROOT/pages/netty-component.adoc b/docs/components/modules/ROOT/pages/netty-component.adoc index f2f2dc7..d3b9716 100644 --- a/docs/components/modules/ROOT/pages/netty-component.adoc +++ b/docs/components/modules/ROOT/pages/netty-component.adoc @@ -62,9 +62,9 @@ The Netty component supports 8 options, which are listed below. [width="100%",cols="2,5,^1,2",options="header"] |=== | Name | Description | Default | Type -| *maximumPoolSize* (advanced) | The thread pool size for the EventExecutorGroup if its in use. The default value is 16. | 16 | int +| *maximumPoolSize* (consumer) | Sets a maximum thread pool size for the netty consumer ordered thread pool. The default size is 2 x cpu core 1. Setting this value to eg 10 will then use 10 threads unless 2 x cpu core 1 is a higher value, which then will override and be used. For example if there are 8 cores, then the consumer thread pool will be 17. This thread pool is used to route messages received from Netty by Camel. We use a separate thread pool to ensure ordering of messages and a [...] | *configuration* (advanced) | To use the NettyConfiguration as configuration when creating endpoints. | | NettyConfiguration -| *executorService* (advanced) | To use the given EventExecutorGroup. | | EventExecutorGroup +| *executorService* (consumer) | To use the given EventExecutorGroup. | | EventExecutorGroup | *useGlobalSslContext Parameters* (security) | Enable usage of global SSL context parameters. | false | boolean | *sslContextParameters* (security) | To configure security using SSLContextParameters | | SSLContextParameters | *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean diff --git a/docs/components/modules/ROOT/pages/netty-http-component.adoc b/docs/components/modules/ROOT/pages/netty-http-component.adoc index f528fe6..ac0f398 100644 --- a/docs/components/modules/ROOT/pages/netty-http-component.adoc +++ b/docs/components/modules/ROOT/pages/netty-http-component.adoc @@ -105,8 +105,8 @@ The Netty HTTP component supports 11 options, which are listed below. | *headerFilterStrategy* (advanced) | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter headers. | | HeaderFilterStrategy | *securityConfiguration* (security) | Refers to a org.apache.camel.component.netty.http.NettyHttpSecurityConfiguration for configuring secure web resources. | | NettyHttpSecurityConfiguration | *useGlobalSslContext Parameters* (security) | Enable usage of global SSL context parameters. | false | boolean -| *maximumPoolSize* (advanced) | The thread pool size for the EventExecutorGroup if its in use. The default value is 16. | 16 | int -| *executorService* (advanced) | To use the given EventExecutorGroup. | | EventExecutorGroup +| *maximumPoolSize* (consumer) | Sets a maximum thread pool size for the netty consumer ordered thread pool. The default size is 2 x cpu core 1. Setting this value to eg 10 will then use 10 threads unless 2 x cpu core 1 is a higher value, which then will override and be used. For example if there are 8 cores, then the consumer thread pool will be 17. This thread pool is used to route messages received from Netty by Camel. We use a separate thread pool to ensure ordering of messages and a [...] +| *executorService* (consumer) | To use the given EventExecutorGroup. | | EventExecutorGroup | *sslContextParameters* (security) | To configure security using SSLContextParameters | | SSLContextParameters | *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean | *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...]
[camel] branch master updated: Add FAQ entry how to create runnable JAR
This is an automated email from the ASF dual-hosted git repository. janbednar pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/camel.git The following commit(s) were added to refs/heads/master by this push: new 1913b85 Add FAQ entry how to create runnable JAR 1913b85 is described below commit 1913b85b0729d9a49b412a46cbe1070504069738 Author: Jan Bednář AuthorDate: Wed Dec 4 17:29:33 2019 +0100 Add FAQ entry how to create runnable JAR --- docs/user-manual/modules/ROOT/pages/faq.adoc | 1 + .../pages/faq/how-to-create-executable-jar.adoc| 33 ++ 2 files changed, 34 insertions(+) diff --git a/docs/user-manual/modules/ROOT/pages/faq.adoc b/docs/user-manual/modules/ROOT/pages/faq.adoc index 7cbc56c..afc9056 100644 --- a/docs/user-manual/modules/ROOT/pages/faq.adoc +++ b/docs/user-manual/modules/ROOT/pages/faq.adoc @@ -97,6 +97,7 @@ Questions on using Apache Camel * xref:faq/how-should-i-package-applications-using-camel-and-activemq.adoc[How should I package applications using Camel and ActiveMQ?] * xref:faq/how-to-avoid-importing-bunch-of-cxf-packages-when-start-up-the-camel-cxf-endpoint-from-osgi-platform-.adoc[How to avoid importing bunch of cxf packages when start up the camel-cxf endpoint from OSGi platform?] * xref:faq/how-to-avoid-sending-some-or-all-message-headers.adoc[How to avoid sending some or all message headers?] +* xref:faq/how-to-create-executable-jar.adoc[How to create executable JAR?] * xref:faq/how-to-define-a-static-camel-converter-method-in-scala.adoc[How to define a static Camel converter method in Scala?] * xref:faq/how-to-remove-the-http-protocol-headers-in-the-camel-message.adoc[How to remove the http protocol headers in the camel message?] * xref:faq/how-to-send-the-same-message-to-multiple-endpoints.adoc[How to send the same message to multiple endpoints?] diff --git a/docs/user-manual/modules/ROOT/pages/faq/how-to-create-executable-jar.adoc b/docs/user-manual/modules/ROOT/pages/faq/how-to-create-executable-jar.adoc new file mode 100644 index 000..50f447c --- /dev/null +++ b/docs/user-manual/modules/ROOT/pages/faq/how-to-create-executable-jar.adoc @@ -0,0 +1,33 @@ +[[HowtocreateexecutableJAR-HowtocreateexecutableJAR]] += How to create executable JAR + +You need to use `maven-shade-plugin` to create executable JAR. + +[source] + + +org.apache.maven.plugins +maven-shade-plugin +3.2.1 + + +package + +shade + + +true +executable-jar + + +my.package.MainClass + + + META-INF/services/org/apache/camel/TypeConverterLoader + + + + + + +
[GitHub] [camel-k] davesargrad commented on issue #1059: camel-k installation struggles
davesargrad commented on issue #1059: camel-k installation struggles URL: https://github.com/apache/camel-k/issues/1059#issuecomment-561717120 As usual... your clue fixed me!!! I had done something dumb in creating the secret.. recreated and all good!! @nicolaferraro .. you da man! This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [camel-k] davesargrad commented on issue #1059: camel-k installation struggles
davesargrad commented on issue #1059: camel-k installation struggles URL: https://github.com/apache/camel-k/issues/1059#issuecomment-561715056 Ty @nicolaferraro Thats extremely useful detail. I did actually see that the maven build seems to have completed successfully, as you say.  I have used the camel-k-secret as you suggest. I've been very particular to reproduce the sequence of commands carefully.  How would I use the -debug variant of the kaniko image? The way I create the sample integration is with: `kamel run Sample.java` This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [camel-k] nicolaferraro commented on issue #1059: camel-k installation struggles
nicolaferraro commented on issue #1059: camel-k installation struggles URL: https://github.com/apache/camel-k/issues/1059#issuecomment-561709089 @davesargrad looking at the first image, the kit is in status "Error", not "ErrImagePull", so it means that it has run the build part and started the docker image packaging part and the logs that you posted are printed by the Kaniko builder. Docker packaging is done by Kaniko at user level in the container, so my guess is that it does not change a lot if you configure the node docker daemon correctly. And I also don't think that the PROXY settings on the host have any effect on the container. In these cases on OpenShift I use `oc debug pod-name` to start an identical pod to the one that failed and try to do some debugging to check the network. You can do a similar thing with Kubernetes. I'd use a `busybox` first to to some connectivity checks: the final destination or the proxy should be reachable, depending on your config. Then if the config is ok and (if needed) your camel k is configured with the --http-proxy-secret as in the messages above, I'd check with the Kaniko image that went in error. Kaniko images have a `-debug` variant, which in our case should be `gcr.io/kaniko-project/executor:debug-v0.9.0`. From that container you can try to build a random Dockerfile from an image of your choice and see what happens. Hope that some suggestions can help your investigations. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [camel-quarkus] lburgazzoli commented on issue #509: Do not use hard coded ports in integration-tests
lburgazzoli commented on issue #509: Do not use hard coded ports in integration-tests URL: https://github.com/apache/camel-quarkus/pull/509#issuecomment-561696289 ok to test This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[camel-k] branch master updated: chore(build): disable go modules when performing go clean
This is an automated email from the ASF dual-hosted git repository. lburgazzoli pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/camel-k.git The following commit(s) were added to refs/heads/master by this push: new 01a8c7f chore(build): disable go modules when performing go clean 01a8c7f is described below commit 01a8c7f565a1a6ea4e1151bba40d5321f4f12765 Author: lburgazzoli AuthorDate: Wed Dec 4 00:34:23 2019 +0100 chore(build): disable go modules when performing go clean --- script/Makefile | 4 1 file changed, 4 insertions(+) diff --git a/script/Makefile b/script/Makefile index 60699d4..b08fc89 100644 --- a/script/Makefile +++ b/script/Makefile @@ -159,6 +159,10 @@ build-compile-integration-tests: go test -c -tags="integration knative" ./e2e/*.go clean: + # disable gomodules when executing go clean: + # + #https://github.com/golang/go/issues/31002 + # go clean rm -f camel-k rm -f kamel
[GitHub] [camel-k] lburgazzoli merged pull request #1118: chore(build): disable go modules when performing go clean
lburgazzoli merged pull request #1118: chore(build): disable go modules when performing go clean URL: https://github.com/apache/camel-k/pull/1118 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [camel-k] davesargrad edited a comment on issue #1059: camel-k installation struggles
davesargrad edited a comment on issue #1059: camel-k installation struggles URL: https://github.com/apache/camel-k/issues/1059#issuecomment-561687601 Guys, I am trying to get camel-k running on yet another k8s cluster. At this point I've gotten reasonably comfortable with camel-k. Of course as typically happens I am struggling yet again with proxy related issues. I dont want to post the details here, but I thought I'd link them here. The issue I created on the kubernetes issue lists shows the failure of the camel-k-kit pod to download an image from the private docker registry I've created. I am pretty sure I've done everything I need to do in order to deal with the proxy. I believe I've followed exactly the procedure that I eventually got working in the past. Yet.. here it rears its ugly head again. The issue on k8s: https://github.com/kubernetes/kubernetes/issues/85904 Please let me know if you guys have suggestions on how to isolate this. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [camel-k] davesargrad commented on issue #1059: camel-k installation struggles
davesargrad commented on issue #1059: camel-k installation struggles URL: https://github.com/apache/camel-k/issues/1059#issuecomment-561687601 Guys, I am trying to get camel-k running on yet another k8s cluster. At this point I've gotten reasonably comfortable with camel-k. Of course as typically happens I am struggling yet again with proxy related issues. I dont want to post the details here, but I thought I'd link them here. The issue I linked on the kubernetes issue lists shows the failure of the camel-k-kit pod to download an image from the private docker registry I've created. I am pretty sure I've done everything I need to do in order to deal with the proxy. I believe I've followed exactly the procedure that I eventually got working in the past. Yet.. here it rears its ugly head again. The issue on k8s: https://github.com/kubernetes/kubernetes/issues/85904 Please let me know if you guys have suggestions on how to isolate this. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [camel-quarkus] lburgazzoli merged pull request #507: Automatically register dozer mapping classes for reflection
lburgazzoli merged pull request #507: Automatically register dozer mapping classes for reflection URL: https://github.com/apache/camel-quarkus/pull/507 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[camel-quarkus] branch master updated: Automatically register dozer mapping classes for reflection
This is an automated email from the ASF dual-hosted git repository.
lburgazzoli pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git
The following commit(s) were added to refs/heads/master by this push:
new 2db85bc Automatically register dozer mapping classes for reflection
2db85bc is described below
commit 2db85bc896a83a385a664afeac157125db348744
Author: James Netherton
AuthorDate: Wed Dec 4 07:49:34 2019 +
Automatically register dozer mapping classes for reflection
---
.../component/dozer/deployment/DozerProcessor.java | 25 +++---
.../component/dozer/it/model/CustomerA.java| 3 ---
.../component/dozer/it/model/CustomerB.java| 3 ---
3 files changed, 17 insertions(+), 14 deletions(-)
diff --git
a/extensions/dozer/deployment/src/main/java/org/apache/camel/quarkus/component/dozer/deployment/DozerProcessor.java
b/extensions/dozer/deployment/src/main/java/org/apache/camel/quarkus/component/dozer/deployment/DozerProcessor.java
index 97551a7..5b37179 100644
---
a/extensions/dozer/deployment/src/main/java/org/apache/camel/quarkus/component/dozer/deployment/DozerProcessor.java
+++
b/extensions/dozer/deployment/src/main/java/org/apache/camel/quarkus/component/dozer/deployment/DozerProcessor.java
@@ -35,6 +35,8 @@ import java.sql.Timestamp;
import java.util.Calendar;
import java.util.Date;
+import com.github.dozermapper.core.DozerBeanMapperBuilder;
+import com.github.dozermapper.core.Mapper;
import
com.github.dozermapper.core.builder.model.jaxb.AllowedExceptionsDefinition;
import com.github.dozermapper.core.builder.model.jaxb.ClassDefinition;
import com.github.dozermapper.core.builder.model.jaxb.ConfigurationDefinition;
@@ -53,10 +55,7 @@ import
com.github.dozermapper.core.builder.model.jaxb.VariableDefinition;
import com.github.dozermapper.core.builder.model.jaxb.VariablesDefinition;
import com.sun.el.ExpressionFactoryImpl;
-import org.apache.camel.component.dozer.CustomMapper;
import org.apache.camel.component.dozer.DozerConfiguration;
-import org.apache.camel.component.dozer.ExpressionMapper;
-import org.apache.camel.component.dozer.VariableMapper;
import org.apache.camel.converter.dozer.DozerBeanMapperConfiguration;
import org.apache.camel.converter.dozer.DozerThreadContextClassLoader;
import org.apache.camel.quarkus.component.dozer.CamelDozerConfig;
@@ -126,11 +125,7 @@ class DozerProcessor {
"com.github.dozermapper.core.builder.model.jaxb.package-info",
"com.sun.org.apache.xerces.internal.impl.dv.xs.SchemaDVFactoryImpl"));
-reflectiveClass.produce(new ReflectiveClassBuildItem(true, false,
-CustomMapper.class,
-DozerConfiguration.class,
-ExpressionMapper.class,
-VariableMapper.class));
+reflectiveClass.produce(new ReflectiveClassBuildItem(true, false,
DozerConfiguration.class));
reflectiveClass.produce(new ReflectiveClassBuildItem(true, true,
AllowedExceptionsDefinition.class,
@@ -149,6 +144,20 @@ class DozerProcessor {
Type.class,
VariableDefinition.class,
VariablesDefinition.class));
+
+if (!camelDozerConfig.mappingFiles.isEmpty()) {
+// Register for reflection any classes participating in Dozer
mapping
+Mapper mapper = DozerBeanMapperBuilder.create()
+.withMappingFiles(camelDozerConfig.mappingFiles)
+.build();
+
+mapper.getMappingMetadata()
+.getClassMappings()
+.stream()
+.map(metadata -> new ReflectiveClassBuildItem(true, false,
metadata.getSourceClassName(),
+metadata.getDestinationClassName()))
+.forEach(reflectiveClass::produce);
+}
}
@Record(ExecutionTime.STATIC_INIT)
diff --git
a/integration-tests/dozer/src/main/java/org/apache/camel/quarkus/component/dozer/it/model/CustomerA.java
b/integration-tests/dozer/src/main/java/org/apache/camel/quarkus/component/dozer/it/model/CustomerA.java
index 139fb56..3f85f79 100644
---
a/integration-tests/dozer/src/main/java/org/apache/camel/quarkus/component/dozer/it/model/CustomerA.java
+++
b/integration-tests/dozer/src/main/java/org/apache/camel/quarkus/component/dozer/it/model/CustomerA.java
@@ -16,9 +16,6 @@
*/
package org.apache.camel.quarkus.component.dozer.it.model;
-import io.quarkus.runtime.annotations.RegisterForReflection;
-
-@RegisterForReflection
public class CustomerA {
private String firstName;
diff --git
a/integration-tests/dozer/src/main/java/org/apache/camel/quarkus/component/dozer/it/model/CustomerB.java
b/integration-tests/dozer/src/main/java/org/apache/camel/quarkus/component/dozer/it/model/CustomerB.java
index bb1da97..dc69c6a 100644
---
[camel-k-runtime] branch master updated: chore: Fix JavaDoc generation on JDK 11
This is an automated email from the ASF dual-hosted git repository.
jamesnetherton pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel-k-runtime.git
The following commit(s) were added to refs/heads/master by this push:
new e627ec2 chore: Fix JavaDoc generation on JDK 11
e627ec2 is described below
commit e627ec2640b8000fb7da968fe9903f5c9bdce286
Author: James Netherton
AuthorDate: Wed Dec 4 14:03:02 2019 +
chore: Fix JavaDoc generation on JDK 11
---
pom.xml | 1 +
1 file changed, 1 insertion(+)
diff --git a/pom.xml b/pom.xml
index a504a9b..d1f34e4 100644
--- a/pom.xml
+++ b/pom.xml
@@ -556,6 +556,7 @@
${javadoc.opts}
+8
[GitHub] [camel-quarkus] lburgazzoli opened a new pull request #509: Do not use hard coded ports in integration-tests
lburgazzoli opened a new pull request #509: Do not use hard coded ports in integration-tests URL: https://github.com/apache/camel-quarkus/pull/509 Fixes #508 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [camel-quarkus] lburgazzoli opened a new issue #508: Do not use hard coded ports in integration-tests
lburgazzoli opened a new issue #508: Do not use hard coded ports in integration-tests URL: https://github.com/apache/camel-quarkus/issues/508 some tests have hard-coded ports in routes definitions, test resources and so on which should be avoided to prevent CI failures This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[camel] branch master updated: CAMEL-14247: camel-netty thread pool for consumer should not be fixed at 16 by default but take into account netty thread pool size and be bigger
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 The following commit(s) were added to refs/heads/master by this push: new ed419c9 CAMEL-14247: camel-netty thread pool for consumer should not be fixed at 16 by default but take into account netty thread pool size and be bigger ed419c9 is described below commit ed419c96a0010bf1a1221c46c9a9bb50ebc589b4 Author: Claus Ibsen AuthorDate: Wed Dec 4 14:53:23 2019 +0100 CAMEL-14247: camel-netty thread pool for consumer should not be fixed at 16 by default but take into account netty thread pool size and be bigger --- .../src/main/docs/netty-http-component.adoc| 4 +-- .../camel-netty/src/main/docs/netty-component.adoc | 4 +-- .../netty/DefaultServerInitializerFactory.java | 2 -- .../camel/component/netty/NettyComponent.java | 39 +++--- .../apache/camel/component/netty/NettyHelper.java | 17 ++ .../NettyHttpComponentConfiguration.java | 12 +-- .../springboot/NettyComponentConfiguration.java| 12 +-- 7 files changed, 59 insertions(+), 31 deletions(-) diff --git a/components/camel-netty-http/src/main/docs/netty-http-component.adoc b/components/camel-netty-http/src/main/docs/netty-http-component.adoc index 79093e0..30a5ee5 100644 --- a/components/camel-netty-http/src/main/docs/netty-http-component.adoc +++ b/components/camel-netty-http/src/main/docs/netty-http-component.adoc @@ -104,8 +104,8 @@ The Netty HTTP component supports 11 options, which are listed below. | *headerFilterStrategy* (advanced) | To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter headers. | | HeaderFilterStrategy | *securityConfiguration* (security) | Refers to a org.apache.camel.component.netty.http.NettyHttpSecurityConfiguration for configuring secure web resources. | | NettyHttpSecurityConfiguration | *useGlobalSslContext Parameters* (security) | Enable usage of global SSL context parameters. | false | boolean -| *maximumPoolSize* (advanced) | The thread pool size for the EventExecutorGroup if its in use. The default value is 16. | 16 | int -| *executorService* (advanced) | To use the given EventExecutorGroup. | | EventExecutorGroup +| *maximumPoolSize* (consumer) | Sets a maximum thread pool size for the netty consumer ordered thread pool. The default size is 2 x cpu core 1. Setting this value to eg 10 will then use 10 threads unless 2 x cpu core 1 is a higher value, which then will override and be used. For example if there are 8 cores, then the consumer thread pool will be 17. This thread pool is used to route messages received from Netty by Camel. We use a separate thread pool to ensure ordering of messages and a [...] +| *executorService* (consumer) | To use the given EventExecutorGroup. | | EventExecutorGroup | *sslContextParameters* (security) | To configure security using SSLContextParameters | | SSLContextParameters | *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean | *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...] diff --git a/components/camel-netty/src/main/docs/netty-component.adoc b/components/camel-netty/src/main/docs/netty-component.adoc index cd23c1d..81ef113 100644 --- a/components/camel-netty/src/main/docs/netty-component.adoc +++ b/components/camel-netty/src/main/docs/netty-component.adoc @@ -61,9 +61,9 @@ The Netty component supports 8 options, which are listed below. [width="100%",cols="2,5,^1,2",options="header"] |=== | Name | Description | Default | Type -| *maximumPoolSize* (advanced) | The thread pool size for the EventExecutorGroup if its in use. The default value is 16. | 16 | int +| *maximumPoolSize* (consumer) | Sets a maximum thread pool size for the netty consumer ordered thread pool. The default size is 2 x cpu core 1. Setting this value to eg 10 will then use 10 threads unless 2 x cpu core 1 is a higher value, which then will override and be used. For example if there are 8 cores, then the consumer thread pool will be 17. This thread pool is used to route messages received from Netty by Camel. We use a separate thread pool to ensure ordering of messages and a [...] | *configuration* (advanced) | To use the NettyConfiguration as configuration when creating endpoints. | | NettyConfiguration -| *executorService*
[GitHub] [camel-quarkus] asf-ci commented on issue #507: Automatically register dozer mapping classes for reflection
asf-ci commented on issue #507: Automatically register dozer mapping classes for reflection URL: https://github.com/apache/camel-quarkus/pull/507#issuecomment-561624771 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/camel-quarkus-pr/467/ This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[camel] branch camel-2.24.x updated: Updating Olingo4
This is an automated email from the ASF dual-hosted git repository. coheigea pushed a commit to branch camel-2.24.x in repository https://gitbox.apache.org/repos/asf/camel.git The following commit(s) were added to refs/heads/camel-2.24.x by this push: new 2d7e717 Updating Olingo4 2d7e717 is described below commit 2d7e717f7ae85cb412a2e8116429d852ef93d670 Author: Colm O hEigeartaigh AuthorDate: Wed Dec 4 11:44:02 2019 + Updating Olingo4 --- parent/pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/parent/pom.xml b/parent/pom.xml index 629f16e..d37910a 100644 --- a/parent/pom.xml +++ b/parent/pom.xml @@ -541,7 +541,7 @@ 2.0.10 2.0.10_1 2.4 -4.4.0 +4.7.0 3.1.12 3.1.12_1 0.12.3
[camel] branch master updated: CAMEL-14224: Fix camel-websocket sendToAll to be faster. Thanks to Michael Elbaz for reporting.
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
The following commit(s) were added to refs/heads/master by this push:
new c14976f CAMEL-14224: Fix camel-websocket sendToAll to be faster.
Thanks to Michael Elbaz for reporting.
c14976f is described below
commit c14976f60cdec821d90f728308e3367371a12d57
Author: Claus Ibsen
AuthorDate: Wed Dec 4 12:47:51 2019 +0100
CAMEL-14224: Fix camel-websocket sendToAll to be faster. Thanks to Michael
Elbaz for reporting.
---
.../component/websocket/WebsocketProducer.java | 23 +-
1 file changed, 9 insertions(+), 14 deletions(-)
diff --git
a/components/camel-websocket/src/main/java/org/apache/camel/component/websocket/WebsocketProducer.java
b/components/camel-websocket/src/main/java/org/apache/camel/component/websocket/WebsocketProducer.java
index 895a0db..8b47d16 100644
---
a/components/camel-websocket/src/main/java/org/apache/camel/component/websocket/WebsocketProducer.java
+++
b/components/camel-websocket/src/main/java/org/apache/camel/component/websocket/WebsocketProducer.java
@@ -129,22 +129,17 @@ public class WebsocketProducer extends DefaultProducer
implements WebsocketProdu
int timeout = endpoint.getSendTimeout();
while (!futures.isEmpty() && watch.taken() < timeout) {
// remove all that are done/cancelled
-for (Future future : futures) {
-if (future.isDone() || future.isCancelled()) {
-futures.remove(future);
-}
-// if there are still more then we need to wait a little bit
before checking again, to avoid burning cpu cycles in the while loop
-if (!futures.isEmpty()) {
-long interval = Math.min(1000, timeout);
-log.debug("Sleeping {} millis waiting for sendToAll to
complete sending with timeout {} millis", interval, timeout);
-try {
-Thread.sleep(interval);
-} catch (InterruptedException e) {
-handleSleepInterruptedException(e, exchange);
-}
+futures.removeIf(future -> future.isDone() ||
future.isCancelled());
+// if there are still more then we need to wait a little bit
before checking again, to avoid burning cpu cycles in the while loop
+if (!futures.isEmpty()) {
+long interval = Math.min(1000, timeout);
+log.debug("Sleeping {} millis waiting for sendToAll to
complete sending with timeout {} millis", interval, timeout);
+try {
+Thread.sleep(interval);
+} catch (InterruptedException e) {
+handleSleepInterruptedException(e, exchange);
}
}
-
}
if (!futures.isEmpty()) {
exception = new WebsocketSendException("Failed to deliver message
within " + endpoint.getSendTimeout() + " millis to one or more recipients.",
exchange);
[camel] branch camel-2.x updated: CAMEL-14224: Fix camel-websocket sendToAll to be faster. Thanks to Michael Elbaz for reporting.
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch camel-2.x
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/camel-2.x by this push:
new cf0b903 CAMEL-14224: Fix camel-websocket sendToAll to be faster.
Thanks to Michael Elbaz for reporting.
cf0b903 is described below
commit cf0b90364a7b91699a741aa78405e5bae2d8a41c
Author: Claus Ibsen
AuthorDate: Wed Dec 4 12:47:51 2019 +0100
CAMEL-14224: Fix camel-websocket sendToAll to be faster. Thanks to Michael
Elbaz for reporting.
---
.../component/websocket/WebsocketProducer.java | 23 +-
1 file changed, 9 insertions(+), 14 deletions(-)
diff --git
a/components/camel-websocket/src/main/java/org/apache/camel/component/websocket/WebsocketProducer.java
b/components/camel-websocket/src/main/java/org/apache/camel/component/websocket/WebsocketProducer.java
index 3392134..eb7eeea 100644
---
a/components/camel-websocket/src/main/java/org/apache/camel/component/websocket/WebsocketProducer.java
+++
b/components/camel-websocket/src/main/java/org/apache/camel/component/websocket/WebsocketProducer.java
@@ -128,22 +128,17 @@ public class WebsocketProducer extends DefaultProducer
implements WebsocketProdu
int timeout = endpoint.getSendTimeout();
while (!futures.isEmpty() && watch.taken() < timeout) {
// remove all that are done/cancelled
-for (Future future : futures) {
-if (future.isDone() || future.isCancelled()) {
-futures.remove(future);
-}
-// if there are still more then we need to wait a little bit
before checking again, to avoid burning cpu cycles in the while loop
-if (!futures.isEmpty()) {
-long interval = Math.min(1000, timeout);
-log.debug("Sleeping {} millis waiting for sendToAll to
complete sending with timeout {} millis", interval, timeout);
-try {
-Thread.sleep(interval);
-} catch (InterruptedException e) {
-handleSleepInterruptedException(e, exchange);
-}
+futures.removeIf(future -> future.isDone() ||
future.isCancelled());
+// if there are still more then we need to wait a little bit
before checking again, to avoid burning cpu cycles in the while loop
+if (!futures.isEmpty()) {
+long interval = Math.min(1000, timeout);
+log.debug("Sleeping {} millis waiting for sendToAll to
complete sending with timeout {} millis", interval, timeout);
+try {
+Thread.sleep(interval);
+} catch (InterruptedException e) {
+handleSleepInterruptedException(e, exchange);
}
}
-
}
if (!futures.isEmpty()) {
exception = new WebsocketSendException("Failed to deliver message
within " + endpoint.getSendTimeout() + " millis to one or more recipients.",
exchange);
[camel] branch camel-2.24.x updated: CAMEL-14224: Fix camel-websocket sendToAll to be faster. Thanks to Michael Elbaz for reporting.
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch camel-2.24.x
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/camel-2.24.x by this push:
new e50b52e CAMEL-14224: Fix camel-websocket sendToAll to be faster.
Thanks to Michael Elbaz for reporting.
e50b52e is described below
commit e50b52e2223d84e9e1602bbddba8730b1797aea4
Author: Claus Ibsen
AuthorDate: Wed Dec 4 12:47:51 2019 +0100
CAMEL-14224: Fix camel-websocket sendToAll to be faster. Thanks to Michael
Elbaz for reporting.
---
.../component/websocket/WebsocketProducer.java | 23 +-
1 file changed, 9 insertions(+), 14 deletions(-)
diff --git
a/components/camel-websocket/src/main/java/org/apache/camel/component/websocket/WebsocketProducer.java
b/components/camel-websocket/src/main/java/org/apache/camel/component/websocket/WebsocketProducer.java
index 3392134..eb7eeea 100644
---
a/components/camel-websocket/src/main/java/org/apache/camel/component/websocket/WebsocketProducer.java
+++
b/components/camel-websocket/src/main/java/org/apache/camel/component/websocket/WebsocketProducer.java
@@ -128,22 +128,17 @@ public class WebsocketProducer extends DefaultProducer
implements WebsocketProdu
int timeout = endpoint.getSendTimeout();
while (!futures.isEmpty() && watch.taken() < timeout) {
// remove all that are done/cancelled
-for (Future future : futures) {
-if (future.isDone() || future.isCancelled()) {
-futures.remove(future);
-}
-// if there are still more then we need to wait a little bit
before checking again, to avoid burning cpu cycles in the while loop
-if (!futures.isEmpty()) {
-long interval = Math.min(1000, timeout);
-log.debug("Sleeping {} millis waiting for sendToAll to
complete sending with timeout {} millis", interval, timeout);
-try {
-Thread.sleep(interval);
-} catch (InterruptedException e) {
-handleSleepInterruptedException(e, exchange);
-}
+futures.removeIf(future -> future.isDone() ||
future.isCancelled());
+// if there are still more then we need to wait a little bit
before checking again, to avoid burning cpu cycles in the while loop
+if (!futures.isEmpty()) {
+long interval = Math.min(1000, timeout);
+log.debug("Sleeping {} millis waiting for sendToAll to
complete sending with timeout {} millis", interval, timeout);
+try {
+Thread.sleep(interval);
+} catch (InterruptedException e) {
+handleSleepInterruptedException(e, exchange);
}
}
-
}
if (!futures.isEmpty()) {
exception = new WebsocketSendException("Failed to deliver message
within " + endpoint.getSendTimeout() + " millis to one or more recipients.",
exchange);
[camel] branch camel-3.0.x updated: CAMEL-14224: Fix camel-websocket sendToAll to be faster. Thanks to Michael Elbaz for reporting.
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a commit to branch camel-3.0.x
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/camel-3.0.x by this push:
new ef46ae3 CAMEL-14224: Fix camel-websocket sendToAll to be faster.
Thanks to Michael Elbaz for reporting.
ef46ae3 is described below
commit ef46ae3d363c54cbf5a67e64958a3b71408aa299
Author: Claus Ibsen
AuthorDate: Wed Dec 4 12:47:51 2019 +0100
CAMEL-14224: Fix camel-websocket sendToAll to be faster. Thanks to Michael
Elbaz for reporting.
---
.../component/websocket/WebsocketProducer.java | 23 +-
1 file changed, 9 insertions(+), 14 deletions(-)
diff --git
a/components/camel-websocket/src/main/java/org/apache/camel/component/websocket/WebsocketProducer.java
b/components/camel-websocket/src/main/java/org/apache/camel/component/websocket/WebsocketProducer.java
index 895a0db..8b47d16 100644
---
a/components/camel-websocket/src/main/java/org/apache/camel/component/websocket/WebsocketProducer.java
+++
b/components/camel-websocket/src/main/java/org/apache/camel/component/websocket/WebsocketProducer.java
@@ -129,22 +129,17 @@ public class WebsocketProducer extends DefaultProducer
implements WebsocketProdu
int timeout = endpoint.getSendTimeout();
while (!futures.isEmpty() && watch.taken() < timeout) {
// remove all that are done/cancelled
-for (Future future : futures) {
-if (future.isDone() || future.isCancelled()) {
-futures.remove(future);
-}
-// if there are still more then we need to wait a little bit
before checking again, to avoid burning cpu cycles in the while loop
-if (!futures.isEmpty()) {
-long interval = Math.min(1000, timeout);
-log.debug("Sleeping {} millis waiting for sendToAll to
complete sending with timeout {} millis", interval, timeout);
-try {
-Thread.sleep(interval);
-} catch (InterruptedException e) {
-handleSleepInterruptedException(e, exchange);
-}
+futures.removeIf(future -> future.isDone() ||
future.isCancelled());
+// if there are still more then we need to wait a little bit
before checking again, to avoid burning cpu cycles in the while loop
+if (!futures.isEmpty()) {
+long interval = Math.min(1000, timeout);
+log.debug("Sleeping {} millis waiting for sendToAll to
complete sending with timeout {} millis", interval, timeout);
+try {
+Thread.sleep(interval);
+} catch (InterruptedException e) {
+handleSleepInterruptedException(e, exchange);
}
}
-
}
if (!futures.isEmpty()) {
exception = new WebsocketSendException("Failed to deliver message
within " + endpoint.getSendTimeout() + " millis to one or more recipients.",
exchange);
[camel] branch camel-2.x updated: Updating Olingo4
This is an automated email from the ASF dual-hosted git repository. coheigea pushed a commit to branch camel-2.x in repository https://gitbox.apache.org/repos/asf/camel.git The following commit(s) were added to refs/heads/camel-2.x by this push: new 42c7191 Updating Olingo4 42c7191 is described below commit 42c71910a6f2880f585dd2458f189efb105cf617 Author: Colm O hEigeartaigh AuthorDate: Wed Dec 4 11:44:02 2019 + Updating Olingo4 --- parent/pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/parent/pom.xml b/parent/pom.xml index 2014789..a54e7ac 100644 --- a/parent/pom.xml +++ b/parent/pom.xml @@ -540,7 +540,7 @@ 2.0.10 2.0.10_1 2.4 -4.4.0 +4.7.0 3.1.12 3.1.12_1 0.12.3
[camel] branch master updated: Updating Olingo4
This is an automated email from the ASF dual-hosted git repository. coheigea pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/camel.git The following commit(s) were added to refs/heads/master by this push: new a00af79 Updating Olingo4 a00af79 is described below commit a00af79c77f7ddf6822a07c69a9599163a0abd37 Author: Colm O hEigeartaigh AuthorDate: Wed Dec 4 11:44:02 2019 + Updating Olingo4 --- parent/pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/parent/pom.xml b/parent/pom.xml index 95f4210..4fad79b 100644 --- a/parent/pom.xml +++ b/parent/pom.xml @@ -492,7 +492,7 @@ 2.0.11 2.0.11_1 2.4 -4.6.0 +4.7.0 3.1.12 3.1.12_1 0.21.0
[camel] branch camel-3.0.x updated: Updating Olingo4
This is an automated email from the ASF dual-hosted git repository. coheigea pushed a commit to branch camel-3.0.x in repository https://gitbox.apache.org/repos/asf/camel.git The following commit(s) were added to refs/heads/camel-3.0.x by this push: new afcbb09 Updating Olingo4 afcbb09 is described below commit afcbb09c1f504456a71bb599c706e21b5d4ced0b Author: Colm O hEigeartaigh AuthorDate: Wed Dec 4 11:44:02 2019 + Updating Olingo4 --- parent/pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/parent/pom.xml b/parent/pom.xml index d27d3b5..fa322e9 100644 --- a/parent/pom.xml +++ b/parent/pom.xml @@ -493,7 +493,7 @@ 2.0.11 2.0.11_1 2.4 -4.6.0 +4.7.0 3.1.12 3.1.12_1 0.21.0
[camel] branch master updated: Allow to add custom decorator to open tracing via java api
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
The following commit(s) were added to refs/heads/master by this push:
new 6b089f8 Allow to add custom decorator to open tracing via java api
6b089f8 is described below
commit 6b089f89c84acc81b0e918cd838f1b2619d75fa4
Author: Claus Ibsen
AuthorDate: Wed Dec 4 12:28:30 2019 +0100
Allow to add custom decorator to open tracing via java api
---
.../apache/camel/opentracing/OpenTracingTracer.java | 21 +
1 file changed, 13 insertions(+), 8 deletions(-)
diff --git
a/components/camel-opentracing/src/main/java/org/apache/camel/opentracing/OpenTracingTracer.java
b/components/camel-opentracing/src/main/java/org/apache/camel/opentracing/OpenTracingTracer.java
index 4a58f11..64a74df 100644
---
a/components/camel-opentracing/src/main/java/org/apache/camel/opentracing/OpenTracingTracer.java
+++
b/components/camel-opentracing/src/main/java/org/apache/camel/opentracing/OpenTracingTracer.java
@@ -70,7 +70,7 @@ import org.apache.camel.util.StringHelper;
@ManagedResource(description = "OpenTracingTracer")
public class OpenTracingTracer extends ServiceSupport implements
RoutePolicyFactory, StaticService, CamelContextAware {
-private static Map decorators = new HashMap<>();
+private static final Map DECORATORS = new
HashMap<>();
private final OpenTracingEventNotifier eventNotifier = new
OpenTracingEventNotifier();
private final OpenTracingLogListener logListener = new
OpenTracingLogListener();
@@ -81,13 +81,13 @@ public class OpenTracingTracer extends ServiceSupport
implements RoutePolicyFact
static {
ServiceLoader.load(SpanDecorator.class).forEach(d -> {
-SpanDecorator existing = decorators.get(d.getComponent());
+SpanDecorator existing = DECORATORS.get(d.getComponent());
// Add span decorator if no existing decorator for the component,
// or if derived from the existing decorator's class, allowing
// custom decorators to be added if they extend the standard
// decorators
if (existing == null || existing.getClass().isInstance(d)) {
-decorators.put(d.getComponent(), d);
+DECORATORS.put(d.getComponent(), d);
}
});
}
@@ -95,6 +95,13 @@ public class OpenTracingTracer extends ServiceSupport
implements RoutePolicyFact
public OpenTracingTracer() {
}
+/**
+ * To add a custom decorator that does not come out of the box with
camel-opentracing.
+ */
+public void addDecorator(SpanDecorator decorator) {
+DECORATORS.put(decorator.getComponent(), decorator);
+}
+
@Override
public RoutePolicy createRoutePolicy(CamelContext camelContext, String
routeId, NamedNode route) {
// ensure this opentracing tracer gets initialized when Camel starts
@@ -109,10 +116,8 @@ public class OpenTracingTracer extends ServiceSupport
implements RoutePolicyFact
public void init(CamelContext camelContext) {
if (!camelContext.hasService(this)) {
try {
-// start this service eager so we init before Camel is starting
-// up
+// start this service eager so we init before Camel is
starting up
camelContext.addService(this, true, true);
-
} catch (Exception e) {
throw RuntimeCamelException.wrapRuntimeCamelException(e);
}
@@ -209,7 +214,7 @@ public class OpenTracingTracer extends ServiceSupport
implements RoutePolicyFact
String splitURI[] = StringHelper.splitOnCharacter(uri, ":", 2);
if (splitURI[1] != null) {
String scheme = splitURI[0];
-sd = decorators.get(scheme);
+sd = DECORATORS.get(scheme);
}
if (sd == null) {
// okay there was no decorator found via component name (scheme),
then try FQN
@@ -217,7 +222,7 @@ public class OpenTracingTracer extends ServiceSupport
implements RoutePolicyFact
Component comp = ((DefaultEndpoint) endpoint).getComponent();
String fqn = comp.getClass().getName();
// lookup via FQN
-sd = decorators.values().stream().filter(d ->
fqn.equals(d.getComponentClassName())).findFirst().orElse(null);
+sd = DECORATORS.values().stream().filter(d ->
fqn.equals(d.getComponentClassName())).findFirst().orElse(null);
}
}
if (sd == null) {
[camel-kafka-connector] branch master updated: Revert "Added readme.md"
This is an automated email from the ASF dual-hosted git repository. acosentino pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/camel-kafka-connector.git The following commit(s) were added to refs/heads/master by this push: new ab4a86a Revert "Added readme.md" ab4a86a is described below commit ab4a86a3c904960960e93243142a04a31743fb12 Author: Andrea Cosentino AuthorDate: Wed Dec 4 12:18:42 2019 +0100 Revert "Added readme.md" This reverts commit ad2bd4dccdb8ac3b339cd94cd764c8ff169ca993. --- README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/README.md b/README.md deleted file mode 100644 index 186c32d..000 --- a/README.md +++ /dev/null @@ -1 +0,0 @@ -Camel-Kafka-connector
[camel-kafka-connector] 01/01: Added readme.md
This is an automated email from the ASF dual-hosted git repository. acosentino pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/camel-kafka-connector.git commit ad2bd4dccdb8ac3b339cd94cd764c8ff169ca993 Author: Andrea Cosentino AuthorDate: Wed Dec 4 12:12:24 2019 +0100 Added readme.md --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md new file mode 100644 index 000..186c32d --- /dev/null +++ b/README.md @@ -0,0 +1 @@ +Camel-Kafka-connector
[camel-kafka-connector] branch master created (now ad2bd4d)
This is an automated email from the ASF dual-hosted git repository. acosentino pushed a change to branch master in repository https://gitbox.apache.org/repos/asf/camel-kafka-connector.git. at ad2bd4d Added readme.md This branch includes the following new commits: new ad2bd4d Added readme.md The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference.
[camel] branch master updated: Fix wording in camel-jdbc prepareStatementStrategy docs
This is an automated email from the ASF dual-hosted git repository.
jamesnetherton pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/master by this push:
new b46a003 Fix wording in camel-jdbc prepareStatementStrategy docs
b46a003 is described below
commit b46a0036f25a167b36b2b871b08c06610cb27344
Author: James Netherton
AuthorDate: Wed Dec 4 11:02:55 2019 +
Fix wording in camel-jdbc prepareStatementStrategy docs
---
components/camel-jdbc/src/main/docs/jdbc-component.adoc | 2 +-
.../src/main/java/org/apache/camel/component/jdbc/JdbcEndpoint.java | 2 +-
.../apache/camel/builder/endpoint/dsl/JdbcEndpointBuilderFactory.java | 4 ++--
docs/components/modules/ROOT/pages/jdbc-component.adoc| 2 +-
4 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/components/camel-jdbc/src/main/docs/jdbc-component.adoc
b/components/camel-jdbc/src/main/docs/jdbc-component.adoc
index c19ecb4..e5e1d88 100644
--- a/components/camel-jdbc/src/main/docs/jdbc-component.adoc
+++ b/components/camel-jdbc/src/main/docs/jdbc-component.adoc
@@ -101,7 +101,7 @@ with the following path and query parameters:
| *useJDBC4ColumnNameAnd LabelSemantics* (producer) | Sets whether to use JDBC
4 or JDBC 3.0 or older semantic when retrieving column name. JDBC 4.0 uses
columnLabel to get the column name where as JDBC 3.0 uses both columnName or
columnLabel. Unfortunately JDBC drivers behave differently so you can use this
option to work out issues around your JDBC driver if you get problem using this
component This option is default true. | true | boolean
| *basicPropertyBinding* (advanced) | Whether the endpoint should use basic
property binding (Camel 2.x) or the newer property binding with additional
capabilities | false | boolean
| *beanRowMapper* (advanced) | To use a custom
org.apache.camel.component.jdbc.BeanRowMapper when using outputClass. The
default implementation will lower case the row names and skip underscores, and
dashes. For example CUST_ID is mapped as custId. | | BeanRowMapper
-| *prepareStatementStrategy* (advanced) | Allows to plugin to use a custom
org.apache.camel.component.jdbc.JdbcPrepareStatementStrategy to control
preparation of the query and prepared statement. | |
JdbcPrepareStatementStrategy
+| *prepareStatementStrategy* (advanced) | Allows the plugin to use a custom
org.apache.camel.component.jdbc.JdbcPrepareStatementStrategy to control
preparation of the query and prepared statement. | |
JdbcPrepareStatementStrategy
| *synchronous* (advanced) | Sets whether synchronous processing should be
strictly used, or Camel is allowed to use asynchronous processing (if
supported). | false | boolean
|===
// endpoint options: END
diff --git
a/components/camel-jdbc/src/main/java/org/apache/camel/component/jdbc/JdbcEndpoint.java
b/components/camel-jdbc/src/main/java/org/apache/camel/component/jdbc/JdbcEndpoint.java
index a45fcd2..20758f8 100644
---
a/components/camel-jdbc/src/main/java/org/apache/camel/component/jdbc/JdbcEndpoint.java
+++
b/components/camel-jdbc/src/main/java/org/apache/camel/component/jdbc/JdbcEndpoint.java
@@ -183,7 +183,7 @@ public class JdbcEndpoint extends DefaultEndpoint {
}
/**
- * Allows to plugin to use a custom
org.apache.camel.component.jdbc.JdbcPrepareStatementStrategy to control
preparation of the query and prepared statement.
+ * Allows the plugin to use a custom
org.apache.camel.component.jdbc.JdbcPrepareStatementStrategy to control
preparation of the query and prepared statement.
*/
public void setPrepareStatementStrategy(JdbcPrepareStatementStrategy
prepareStatementStrategy) {
this.prepareStatementStrategy = prepareStatementStrategy;
diff --git
a/core/camel-endpointdsl/src/main/java/org/apache/camel/builder/endpoint/dsl/JdbcEndpointBuilderFactory.java
b/core/camel-endpointdsl/src/main/java/org/apache/camel/builder/endpoint/dsl/JdbcEndpointBuilderFactory.java
index cb6e72b..d9e1476 100644
---
a/core/camel-endpointdsl/src/main/java/org/apache/camel/builder/endpoint/dsl/JdbcEndpointBuilderFactory.java
+++
b/core/camel-endpointdsl/src/main/java/org/apache/camel/builder/endpoint/dsl/JdbcEndpointBuilderFactory.java
@@ -405,7 +405,7 @@ public interface JdbcEndpointBuilderFactory {
return this;
}
/**
- * Allows to plugin to use a custom
+ * Allows the plugin to use a custom
* org.apache.camel.component.jdbc.JdbcPrepareStatementStrategy to
* control preparation of the query and prepared statement.
*
@@ -420,7 +420,7 @@ public interface JdbcEndpointBuilderFactory {
return this;
}
/**
- * Allows to plugin to use a custom
+ * Allows the plugin to use a custom
* org.apache.camel.component.jdbc.JdbcPrepareStatementStrategy to
* control
[camel] 01/02: Camel-AWS Translate: Fixed endpoint description
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 03dffbfa502f055587c577b88f262f8789b6adbb
Author: Andrea Cosentino
AuthorDate: Wed Dec 4 10:57:56 2019 +0100
Camel-AWS Translate: Fixed endpoint description
---
.../org/apache/camel/component/aws/translate/TranslateEndpoint.java | 2 +-
.../camel/builder/endpoint/dsl/TranslateEndpointBuilderFactory.java | 4 ++--
.../aws/translate/springboot/TranslateComponentConfiguration.java | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git
a/components/camel-aws-translate/src/main/java/org/apache/camel/component/aws/translate/TranslateEndpoint.java
b/components/camel-aws-translate/src/main/java/org/apache/camel/component/aws/translate/TranslateEndpoint.java
index fd3cc8c..d19a20c 100644
---
a/components/camel-aws-translate/src/main/java/org/apache/camel/component/aws/translate/TranslateEndpoint.java
+++
b/components/camel-aws-translate/src/main/java/org/apache/camel/component/aws/translate/TranslateEndpoint.java
@@ -34,7 +34,7 @@ import org.apache.camel.support.ScheduledPollEndpoint;
import org.apache.camel.util.ObjectHelper;
/**
- * The aws-kms is used for managing Amazon Translate
+ * The aws-translate component is used for managing Amazon Translate
*/
@UriEndpoint(firstVersion = "3.0.0", scheme = "aws-translate", title = "AWS
Translate", syntax = "aws-translate:label", producerOnly = true, label =
"cloud,management")
public class TranslateEndpoint extends ScheduledPollEndpoint {
diff --git
a/core/camel-endpointdsl/src/main/java/org/apache/camel/builder/endpoint/dsl/TranslateEndpointBuilderFactory.java
b/core/camel-endpointdsl/src/main/java/org/apache/camel/builder/endpoint/dsl/TranslateEndpointBuilderFactory.java
index af22054..df2f8f1 100644
---
a/core/camel-endpointdsl/src/main/java/org/apache/camel/builder/endpoint/dsl/TranslateEndpointBuilderFactory.java
+++
b/core/camel-endpointdsl/src/main/java/org/apache/camel/builder/endpoint/dsl/TranslateEndpointBuilderFactory.java
@@ -22,7 +22,7 @@ import org.apache.camel.builder.EndpointProducerBuilder;
import org.apache.camel.builder.endpoint.AbstractEndpointBuilder;
/**
- * The aws-kms is used for managing Amazon Translate
+ * The aws-translate component is used for managing Amazon Translate
*
* Generated by camel-package-maven-plugin - do not edit this file!
*/
@@ -325,7 +325,7 @@ public interface TranslateEndpointBuilderFactory {
}
/**
* AWS Translate (camel-aws-translate)
- * The aws-kms is used for managing Amazon Translate
+ * The aws-translate component is used for managing Amazon Translate
*
* Category: cloud,management
* Since: 3.0
diff --git
a/platforms/spring-boot/components-starter/camel-aws-translate-starter/src/main/java/org/apache/camel/component/aws/translate/springboot/TranslateComponentConfiguration.java
b/platforms/spring-boot/components-starter/camel-aws-translate-starter/src/main/java/org/apache/camel/component/aws/translate/springboot/TranslateComponentConfiguration.java
index bf94853..3b328b7 100644
---
a/platforms/spring-boot/components-starter/camel-aws-translate-starter/src/main/java/org/apache/camel/component/aws/translate/springboot/TranslateComponentConfiguration.java
+++
b/platforms/spring-boot/components-starter/camel-aws-translate-starter/src/main/java/org/apache/camel/component/aws/translate/springboot/TranslateComponentConfiguration.java
@@ -24,7 +24,7 @@ import
org.apache.camel.spring.boot.ComponentConfigurationPropertiesCommon;
import org.springframework.boot.context.properties.ConfigurationProperties;
/**
- * The aws-kms is used for managing Amazon Translate
+ * The aws-translate component is used for managing Amazon Translate
*
* Generated by camel-package-maven-plugin - do not edit this file!
*/
[camel] branch master updated (1986883 -> 9bdd116)
This is an automated email from the ASF dual-hosted git repository. acosentino pushed a change to branch master in repository https://gitbox.apache.org/repos/asf/camel.git. from 1986883 Merge pull request #3382 from apupier/patch-3 new 03dffbf Camel-AWS Translate: Fixed endpoint description new 9bdd116 Regen docs The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: .../org/apache/camel/component/aws/translate/TranslateEndpoint.java | 2 +- .../camel/builder/endpoint/dsl/TranslateEndpointBuilderFactory.java | 4 ++-- docs/components/modules/ROOT/pages/index.adoc | 2 +- .../aws/translate/springboot/TranslateComponentConfiguration.java | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-)
[camel] 02/02: Regen docs
This is an automated email from the ASF dual-hosted git repository. acosentino pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/camel.git commit 9bdd1165518546c67566835ae221de613687bf9a Author: Andrea Cosentino AuthorDate: Wed Dec 4 11:12:46 2019 +0100 Regen docs --- docs/components/modules/ROOT/pages/index.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/components/modules/ROOT/pages/index.adoc b/docs/components/modules/ROOT/pages/index.adoc index c06978c..e25351b 100644 --- a/docs/components/modules/ROOT/pages/index.adoc +++ b/docs/components/modules/ROOT/pages/index.adoc @@ -84,7 +84,7 @@ Number of Components: 305 in 243 JAR artifacts (0 deprecated) | xref:aws-sdb-component.adoc[AWS SimpleDB] (camel-aws-sdb) | 2.9 | The aws-sdb component is for storing and retrieving data from/to Amazon's SDB service. -| xref:aws-translate-component.adoc[AWS Translate] (camel-aws-translate) | 3.0 | The aws-kms is used for managing Amazon Translate +| xref:aws-translate-component.adoc[AWS Translate] (camel-aws-translate) | 3.0 | The aws-translate component is used for managing Amazon Translate | xref:azure-blob-component.adoc[Azure Storage Blob Service] (camel-azure) | 2.19 | The azure-blob component is used for storing and retrieving blobs from Azure Storage Blob Service.
[camel] branch master updated: Remove dead link to javadoc of ExchangePattern
This is an automated email from the ASF dual-hosted git repository. acosentino pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/camel.git The following commit(s) were added to refs/heads/master by this push: new 6ccce21 Remove dead link to javadoc of ExchangePattern new 1986883 Merge pull request #3382 from apupier/patch-3 6ccce21 is described below commit 6ccce2182eab5c6ab6e55038aef4c7519704a6eb Author: Aurélien Pupier AuthorDate: Wed Dec 4 11:05:25 2019 +0100 Remove dead link to javadoc of ExchangePattern use the fully qualified name so that users can find the enumeration easily as the information is no more available from the link that is removed. --- docs/user-manual/modules/ROOT/pages/exchange-pattern.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-manual/modules/ROOT/pages/exchange-pattern.adoc b/docs/user-manual/modules/ROOT/pages/exchange-pattern.adoc index 5151b3d..1718660 100644 --- a/docs/user-manual/modules/ROOT/pages/exchange-pattern.adoc +++ b/docs/user-manual/modules/ROOT/pages/exchange-pattern.adoc @@ -11,7 +11,7 @@ Integration Patterns] the common examples are * Event Message (or one way) In Camel we have an -http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/ExchangePattern.html[ExchangePattern] +`org.apache.camel.ExchangePattern` enumeration which can be configured on the *exchangePattern* property on the Message Exchange indicating if a message exchange is a one way Event Message (InOnly) or
[camel] branch master updated: Upgrade Jgroups Raft to version 0.5.1.Final
This is an automated email from the ASF dual-hosted git repository. acosentino pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/camel.git The following commit(s) were added to refs/heads/master by this push: new 2f79624 Upgrade Jgroups Raft to version 0.5.1.Final 2f79624 is described below commit 2f7962446ff2a6e32aeb7f341c6f47538b32d57d Author: Andrea Cosentino AuthorDate: Wed Dec 4 10:40:06 2019 +0100 Upgrade Jgroups Raft to version 0.5.1.Final --- parent/pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/parent/pom.xml b/parent/pom.xml index 106416b..95f4210 100644 --- a/parent/pom.xml +++ b/parent/pom.xml @@ -354,7 +354,7 @@ 1.4.0 5.5.1.201910021850-r 4.1.8.Final -0.5.0.Final +0.5.1.Final 1.8 1.0.8 26.0-jre
[camel-quarkus] branch master updated: [maven-release-plugin] prepare for next development iteration
This is an automated email from the ASF dual-hosted git repository. acosentino pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git The following commit(s) were added to refs/heads/master by this push: new f38d426 [maven-release-plugin] prepare for next development iteration f38d426 is described below commit f38d426620b565f42a47a9b1fde8c59046b0e2f5 Author: Andrea Cosentino AuthorDate: Wed Dec 4 10:51:03 2019 +0100 [maven-release-plugin] prepare for next development iteration --- catalog/camel-quarkus-catalog/pom.xml | 2 +- catalog/pom.xml| 2 +- docs/pom.xml | 2 +- examples/observability/pom.xml | 2 +- examples/pom.xml | 2 +- examples/rest-json/pom.xml | 2 +- examples/timer-log-cdi/pom.xml | 2 +- examples/timer-log-spring/pom.xml | 2 +- examples/timer-log-xml/pom.xml | 2 +- examples/timer-log/pom.xml | 2 +- extensions/attachments/deployment/pom.xml | 2 +- extensions/attachments/pom.xml | 2 +- extensions/attachments/runtime/pom.xml | 2 +- extensions/aws-ecs/deployment/pom.xml | 2 +- extensions/aws-ecs/pom.xml | 2 +- extensions/aws-ecs/runtime/pom.xml | 2 +- extensions/aws-eks/deployment/pom.xml | 2 +- extensions/aws-eks/pom.xml | 2 +- extensions/aws-eks/runtime/pom.xml | 2 +- extensions/aws-kms/deployment/pom.xml | 2 +- extensions/aws-kms/pom.xml | 2 +- extensions/aws-kms/runtime/pom.xml | 2 +- extensions/aws-s3/deployment/pom.xml | 2 +- extensions/aws-s3/pom.xml | 2 +- extensions/aws-s3/runtime/pom.xml | 2 +- extensions/aws-sns/deployment/pom.xml | 2 +- extensions/aws-sns/pom.xml | 2 +- extensions/aws-sns/runtime/pom.xml | 2 +- extensions/aws-sqs/deployment/pom.xml | 2 +- extensions/aws-sqs/pom.xml | 2 +- extensions/aws-sqs/runtime/pom.xml | 2 +- extensions/base64/deployment/pom.xml | 2 +- extensions/base64/pom.xml | 2 +- extensions/base64/runtime/pom.xml | 2 +- extensions/bean-validator/deployment/pom.xml | 2 +- extensions/bean-validator/pom.xml | 2 +- extensions/bean-validator/runtime/pom.xml | 2 +- extensions/bean/deployment/pom.xml | 2 +- extensions/bean/pom.xml| 2 +- extensions/bean/runtime/pom.xml| 2 +- extensions/controlbus/deployment/pom.xml | 2 +- extensions/controlbus/pom.xml | 2 +- extensions/controlbus/runtime/pom.xml | 2 +- extensions/core-cloud/deployment/pom.xml | 2 +- extensions/core-cloud/pom.xml | 2 +- extensions/core-cloud/runtime/pom.xml | 2 +- extensions/core-xml/deployment/pom.xml | 2 +- extensions/core-xml/pom.xml| 2 +- extensions/core-xml/runtime/pom.xml| 2 +- extensions/core/deployment/pom.xml | 2 +- extensions/core/pom.xml| 2 +- extensions/core/runtime/pom.xml| 2 +- extensions/csv/deployment/pom.xml | 2 +- extensions/csv/pom.xml | 2 +- extensions/csv/runtime/pom.xml | 2 +- extensions/dataformat/deployment/pom.xml | 2 +- extensions/dataformat/pom.xml | 2 +- extensions/dataformat/runtime/pom.xml | 2 +- extensions/direct/deployment/pom.xml | 2 +- extensions/direct/pom.xml | 2 +- extensions/direct/runtime/pom.xml | 2 +- extensions/dozer/deployment/pom.xml| 2 +- extensions/dozer/pom.xml | 2 +- extensions/dozer/runtime/pom.xml | 2 +- extensions/exec/deployment/pom.xml | 2 +- extensions/exec/pom.xml| 2 +- extensions/exec/runtime/pom.xml| 2 +- extensions/fhir/deployment/pom.xml | 2 +- extensions/fhir/pom.xml| 2 +- extensions/fhir/runtime/pom.xml| 2 +- extensions/file/deployment/pom.xml
[camel-quarkus] annotated tag 1.0.0-M1 created (now d7ad515)
This is an automated email from the ASF dual-hosted git repository. acosentino pushed a change to annotated tag 1.0.0-M1 in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git. at d7ad515 (tag) tagging eaae8bb2e6b09247ac37db1393bcb0d1d926706c (commit) replaces 0.4.0 by Andrea Cosentino on Wed Dec 4 10:50:56 2019 +0100 - Log - [maven-release-plugin] copy for tag 1.0.0-M1 --- No new revisions were added by this update.
[GitHub] [camel-quarkus] davsclaus commented on issue #505: camel-sql extension
davsclaus commented on issue #505: camel-sql extension URL: https://github.com/apache/camel-quarkus/issues/505#issuecomment-561559450 the sql component is just much more powerful than jdbc so it would have been nice This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [camel-quarkus] davsclaus commented on issue #505: camel-sql extension
davsclaus commented on issue #505: camel-sql extension URL: https://github.com/apache/camel-quarkus/issues/505#issuecomment-561559355 Ah yeah a camel-jpa extension would be great This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [camel-quarkus] lburgazzoli commented on issue #505: camel-sql extension
lburgazzoli commented on issue #505: camel-sql extension URL: https://github.com/apache/camel-quarkus/issues/505#issuecomment-561558118 As far as I can remember the spring compatibility does not use any spring bits but translates spring concerns into the related quarkus/hibernate bits This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [camel-quarkus] jamesnetherton commented on issue #505: camel-sql extension
jamesnetherton commented on issue #505: camel-sql extension URL: https://github.com/apache/camel-quarkus/issues/505#issuecomment-561556762 Isn't Quarkus Spring Data more JPA focussed? So maybe better suited to camel-jpa? We already have a camel-jdbc extension, so implementing camel-sql should be simple enough. I'm happy to work on it (and camel-jpa if we want to add an extension for it). This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[camel] branch master updated: Regen
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/master by this push:
new 46e1e4e Regen
46e1e4e is described below
commit 46e1e4ec7e6e222ead1c3802b83f5e0bae50f19e
Author: Andrea Cosentino
AuthorDate: Wed Dec 4 10:18:56 2019 +0100
Regen
---
bom/camel-bom/pom.xml | 10 +-
.../spring-boot-dm/camel-spring-boot-dependencies/pom.xml | 10 +-
2 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/bom/camel-bom/pom.xml b/bom/camel-bom/pom.xml
index 035d811..b20d26c 100644
--- a/bom/camel-bom/pom.xml
+++ b/bom/camel-bom/pom.xml
@@ -1929,6 +1929,11 @@
org.apache.camel
+camel-core-osgi-activator
+${project.version}
+
+
+org.apache.camel
camel-core-xml
${project.version}
@@ -2544,11 +2549,6 @@
org.apache.camel
-camel-main-osgi
-${project.version}
-
-
-org.apache.camel
camel-management
${project.version}
diff --git
a/platforms/spring-boot/spring-boot-dm/camel-spring-boot-dependencies/pom.xml
b/platforms/spring-boot/spring-boot-dm/camel-spring-boot-dependencies/pom.xml
index 77de07c..c661fcf 100644
---
a/platforms/spring-boot/spring-boot-dm/camel-spring-boot-dependencies/pom.xml
+++
b/platforms/spring-boot/spring-boot-dm/camel-spring-boot-dependencies/pom.xml
@@ -2149,6 +2149,11 @@
org.apache.camel
+camel-core-osgi-activator
+${project.version}
+
+
+org.apache.camel
camel-core-xml
${project.version}
@@ -2764,11 +2769,6 @@
org.apache.camel
-camel-main-osgi
-${project.version}
-
-
-org.apache.camel
camel-management
${project.version}
[camel-quarkus] branch master updated (ef44422 -> ac9f96c)
This is an automated email from the ASF dual-hosted git repository.
davsclaus pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git.
from ef44422 Update contributor-guide.adoc
add ac9f96c feat: base64 extension (#506)
No new revisions were added by this update.
Summary of changes:
.../pages/list-of-camel-quarkus-extensions.adoc| 4 +++-
extensions/{seda => base64}/deployment/pom.xml | 8
.../base64/deployment/Base64Processor.java}| 6 +++---
extensions/{ftp => base64}/pom.xml | 4 ++--
extensions/{ftp => base64}/runtime/pom.xml | 14 ++---
.../main/resources/META-INF/quarkus-extension.yaml | 4 ++--
extensions/pom.xml | 1 +
extensions/readme.adoc | 4 +++-
.../{bean-validator => base64}/pom.xml | 8
.../component/base64/it/Base64Resource.java} | 23 --
.../component/base64/it/Base64RouteBuilder.java| 9 +
.../quarkus/component/base64/it/Base64IT.java} | 4 ++--
.../quarkus/component/base64/it/Base64Test.java| 22 ++---
integration-tests/pom.xml | 1 +
.../component/zipfile/it/ZipfileRouteBuilder.java | 1 -
poms/bom-deployment/pom.xml| 5 +
poms/bom/pom.xml | 10 ++
17 files changed, 76 insertions(+), 52 deletions(-)
copy extensions/{seda => base64}/deployment/pom.xml (91%)
copy
extensions/{bean/deployment/src/main/java/org/apache/camel/quarkus/component/bean/deployment/BeanProcessor.java
=>
base64/deployment/src/main/java/org/apache/camel/quarkus/component/base64/deployment/Base64Processor.java}
(87%)
copy extensions/{ftp => base64}/pom.xml (93%)
copy extensions/{ftp => base64}/runtime/pom.xml (93%)
copy extensions/{dataformat =>
base64}/runtime/src/main/resources/META-INF/quarkus-extension.yaml (90%)
copy integration-tests/{bean-validator => base64}/pom.xml (94%)
copy
integration-tests/{zipfile/src/main/java/org/apache/camel/quarkus/component/zipfile/it/ZipfileResource.java
=>
base64/src/main/java/org/apache/camel/quarkus/component/base64/it/Base64Resource.java}
(70%)
copy examples/timer-log/src/main/java/org/acme/timer/TimerRoute.java =>
integration-tests/base64/src/main/java/org/apache/camel/quarkus/component/base64/it/Base64RouteBuilder.java
(82%)
copy
integration-tests/{csv/src/test/java/org/apache/camel/quarkus/component/csv/it/CsvIT.java
=>
base64/src/test/java/org/apache/camel/quarkus/component/base64/it/Base64IT.java}
(90%)
copy tooling/create-extension-templates/Test.java =>
integration-tests/base64/src/test/java/org/apache/camel/quarkus/component/base64/it/Base64Test.java
(67%)
[GitHub] [camel-quarkus] davsclaus merged pull request #506: feat: base64 extension
davsclaus merged pull request #506: feat: base64 extension URL: https://github.com/apache/camel-quarkus/pull/506 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] [camel-quarkus] asf-ci commented on issue #506: feat: base64 extension
asf-ci commented on issue #506: feat: base64 extension URL: https://github.com/apache/camel-quarkus/pull/506#issuecomment-561548475 Refer to this link for build results (access rights to CI server needed): https://builds.apache.org/job/camel-quarkus-pr/466/ This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[camel] 01/04: CAMEL-14253: camel-nats - Configure brokers on component level
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 6f2ad84616da2ba30c43b998b5f3b57fc86acc89 Author: Claus Ibsen AuthorDate: Wed Dec 4 10:00:27 2019 +0100 CAMEL-14253: camel-nats - Configure brokers on component level --- .../camel-nats/src/main/docs/nats-component.adoc | 15 +- .../apache/camel/component/nats/NatsComponent.java | 18 +- .../camel/component/nats/NatsConfiguration.java| 20 +-- .../apache/camel/component/nats/NatsConsumer.java | 1 - .../apache/camel/component/nats/NatsEndpoint.java | 6 +- .../apache/camel/component/nats/NatsProducer.java | 1 + .../component/nats/NatsAuthConsumerLoadTest.java | 4 +- .../camel/component/nats/NatsAuthProducerTest.java | 3 +- .../camel/component/nats/NatsAuthTestSupport.java | 11 +- .../nats/NatsAuthTokenConsumerLoadTest.java| 4 +- .../component/nats/NatsAuthTokenProducerTest.java | 3 +- .../component/nats/NatsAuthTokenTestSupport.java | 12 +- .../camel/component/nats/NatsConsumerLoadTest.java | 9 +- .../nats/NatsConsumerMaxMessagesQueueTest.java | 8 +- .../nats/NatsConsumerMaxMessagesTest.java | 5 +- .../component/nats/NatsConsumerReplyToTest.java| 6 +- .../camel/component/nats/NatsConsumerTest.java | 5 +- .../nats/NatsConsumerWithConnectionLoadTest.java | 15 +- .../nats/NatsConsumerWithRedeliveryTest.java | 17 +- .../camel/component/nats/NatsProducerTLSTest.java | 3 +- .../camel/component/nats/NatsProducerTest.java | 3 +- .../camel/component/nats/NatsTestSupport.java | 11 +- .../endpoint/dsl/NatsEndpointBuilderFactory.java | 185 ++--- .../modules/ROOT/pages/nats-component.adoc | 35 ++-- .../springboot/NatsComponentConfiguration.java | 13 ++ 25 files changed, 238 insertions(+), 175 deletions(-) diff --git a/components/camel-nats/src/main/docs/nats-component.adoc b/components/camel-nats/src/main/docs/nats-component.adoc index ff05266..8ee8984 100644 --- a/components/camel-nats/src/main/docs/nats-component.adoc +++ b/components/camel-nats/src/main/docs/nats-component.adoc @@ -35,13 +35,14 @@ Where *servers* represents the list of NATS servers. // component options: START -The Nats component supports 4 options, which are listed below. +The Nats component supports 5 options, which are listed below. [width="100%",cols="2,5,^1,2",options="header"] |=== | Name | Description | Default | Type +| *servers* (common) | URLs to one or more NAT servers. Use comma to separate URLs when specifying multiple servers. | | String | *useGlobalSslContext Parameters* (security) | Enable usage of global SSL context parameters. | false | boolean | *basicPropertyBinding* (advanced) | Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean | *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and [...] @@ -57,7 +58,7 @@ The Nats component supports 4 options, which are listed below. The Nats endpoint is configured using URI syntax: -nats:servers +nats:topic with the following path and query parameters: @@ -68,7 +69,7 @@ with the following path and query parameters: [width="100%",cols="2,5,^1,2",options="header"] |=== | Name | Description | Default | Type -| *servers* | *Required* URLs to one or more NAT servers. Use comma to separate URLs when specifying multiple servers. | | String +| *topic* | *Required* The name of topic we want to use | | String |=== @@ -78,9 +79,8 @@ with the following path and query parameters: [width="100%",cols="2,5,^1,2",options="header"] |=== | Name | Description | Default | Type -| *connection* (common) | Reference an already instantiated connection to Nats server | | Connection | *connectionTimeout* (common) | Timeout for connection attempts. (in milliseconds) | 2000 | int -| *flushConnection* (common) | Define if we want to flush connection or not | false | boolean +| *flushConnection* (common) | Define if we want to flush connection when stopping or not | false | boolean | *flushTimeout* (common) | Set the flush timeout (in milliseconds) | 1000 | int | *maxPingsOut* (common) | maximum number of pings have not received a response allowed by the client | 2 | int | *maxReconnectAttempts* (common) | Max reconnection attempts | 60 | int @@ -91,11 +91,11 @@ with the following path and query
[camel] 03/04: CAMEL-14253: camel-nats - Configure brokers on component level
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 725fed6e733ccf756217a4ddbbf547d9fa7600bd
Author: Claus Ibsen
AuthorDate: Wed Dec 4 10:10:31 2019 +0100
CAMEL-14253: camel-nats - Configure brokers on component level
---
.../camel-nats/src/main/docs/nats-component.adoc | 72 +-
.../camel/component/nats/NatsAuthTestSupport.java | 2 +-
.../component/nats/NatsAuthTokenTestSupport.java | 2 +-
.../camel/component/nats/NatsTestSupport.java | 2 +-
.../modules/ROOT/pages/nats-component.adoc | 72 +-
5 files changed, 117 insertions(+), 33 deletions(-)
diff --git a/components/camel-nats/src/main/docs/nats-component.adoc
b/components/camel-nats/src/main/docs/nats-component.adoc
index 8ee8984..bc340ac 100644
--- a/components/camel-nats/src/main/docs/nats-component.adoc
+++ b/components/camel-nats/src/main/docs/nats-component.adoc
@@ -26,10 +26,10 @@ their `pom.xml` for this component.
[source,java]
--
-nats:servers[?options]
+nats:topic[?options]
--
-Where *servers* represents the list of NATS servers.
+Where *topic* is the topic name
== Options
@@ -125,7 +125,7 @@ When using Spring Boot make sure to use the following Maven
dependency to have s
-The component supports 5 options, which are listed below.
+The component supports 6 options, which are listed below.
@@ -136,13 +136,51 @@ The component supports 5 options, which are listed below.
| *camel.component.nats.bridge-error-handler* | Allows for bridging the
consumer to the Camel routing Error Handler, which mean any exceptions occurred
while the consumer is trying to pickup incoming messages, or the likes, will
now be processed as a message and handled by the routing Error Handler. By
default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal
with exceptions, that will be logged at WARN or ERROR level and ignored. |
false | Boolean
| *camel.component.nats.enabled* | Whether to enable auto configuration of the
nats component. This is enabled by default. | | Boolean
| *camel.component.nats.lazy-start-producer* | Whether the producer should be
started lazy (on the first message). By starting lazy you can use this to allow
CamelContext and routes to startup in situations where a producer may otherwise
fail during starting and cause the route to fail being started. By deferring
this startup to be lazy then the startup failure can be handled during routing
messages via Camel's routing error handlers. Beware that when the first message
is processed then [...]
+| *camel.component.nats.servers* | URLs to one or more NAT servers. Use comma
to separate URLs when specifying multiple servers. | | String
| *camel.component.nats.use-global-ssl-context-parameters* | Enable usage of
global SSL context parameters. | false | Boolean
|===
// spring-boot-auto-configure options: END
+== Configuring servers
+You configure the NATS servers on either the component or the endpoint.
+For example to configure this once on the component you can do:
+
+[source,java]
+
+NatsComponent nats = context.getComponent("nats", NatsComponent.class);
+nats.setServers("someserver:4222,someotherserver:4");
+
+
+Notice how you can specify multiple servers separated by comma.
+
+Or you can specify the servers in the endpoint URI
+
+[source,java]
+
+from("direct:send").to("nats:test?servers=localhost:4222");
+
+
+The endpoint configuration will override any server configuration on the
component level.
+
+=== Configuring username and password or token
+
+You can specify username and password for the servers in the server URLs,
+where its `username:password@url`, or `token@url` etc:
+
+[source,java]
+
+NatsComponent nats = context.getComponent("nats", NatsComponent.class);
+nats.setServers("scott:tiger@someserver:4222,superman:123@someotherserver:4");
+
+
+If you are using Camel Main or Spring Boot you can configure the server urls
in the `application.properties` file
+[source,properties]
+
+camel.component.nats.servers=scott:tiger@someserver:4222,superman:123@someotherserver:4
+
== Headers
@@ -167,27 +205,31 @@ The consumer will when routing the message is complete,
send back the message as
*Producer example:*
[source,java]
-from("direct:send").to("nats://localhost:4222?topic=test");
+
+from("direct:send")
+ .to("nats:mytopic");
+
In case of using Authorization you can directly specify your credentials in
the server URL
[source,java]
-from("direct:send").to("nats://username:password@localhost:4222?topic=test");
[camel] 02/04: Regen
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 ec710873d604d364947f56573830e3449151ab56 Author: Claus Ibsen AuthorDate: Wed Dec 4 10:00:33 2019 +0100 Regen --- docs/components/modules/ROOT/pages/rest-swagger-component.adoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/components/modules/ROOT/pages/rest-swagger-component.adoc b/docs/components/modules/ROOT/pages/rest-swagger-component.adoc index 683f809..725b58b 100644 --- a/docs/components/modules/ROOT/pages/rest-swagger-component.adoc +++ b/docs/components/modules/ROOT/pages/rest-swagger-component.adoc @@ -127,7 +127,7 @@ with the following path and query parameters: |=== -=== Query Parameters (8 parameters): +=== Query Parameters (9 parameters): [width="100%",cols="2,5,^1,2",options="header"] @@ -141,6 +141,7 @@ with the following path and query parameters: | *produces* (producer) | What payload type this component is producing. For example application/json according to the RFC7231. This equates to the value of Content-Type HTTP header. If set overrides any value present in the Swagger specification. Overrides all other configuration. | | String | *basicPropertyBinding* (advanced) | Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities | false | boolean | *synchronous* (advanced) | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | boolean +| *sslContextParameters* (security) | To configure security using SSLContextParameters. | | SSLContextParameters |=== // endpoint options: END // spring-boot-auto-configure options: START
[camel] 04/04: CAMEL-14253: camel-nats - Configure brokers on component level
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 17552976c0692a4b34536c484b2e3d24be1b3f9c
Author: Claus Ibsen
AuthorDate: Wed Dec 4 10:12:14 2019 +0100
CAMEL-14253: camel-nats - Configure brokers on component level
---
.../apache/camel/opentracing/decorators/NatsSpanDecorator.java | 10 --
1 file changed, 10 deletions(-)
diff --git
a/components/camel-opentracing/src/main/java/org/apache/camel/opentracing/decorators/NatsSpanDecorator.java
b/components/camel-opentracing/src/main/java/org/apache/camel/opentracing/decorators/NatsSpanDecorator.java
index dfa3262..0882576 100644
---
a/components/camel-opentracing/src/main/java/org/apache/camel/opentracing/decorators/NatsSpanDecorator.java
+++
b/components/camel-opentracing/src/main/java/org/apache/camel/opentracing/decorators/NatsSpanDecorator.java
@@ -16,9 +16,6 @@
*/
package org.apache.camel.opentracing.decorators;
-import java.util.Map;
-
-import org.apache.camel.Endpoint;
import org.apache.camel.Exchange;
public class NatsSpanDecorator extends AbstractMessagingSpanDecorator {
@@ -36,13 +33,6 @@ public class NatsSpanDecorator extends
AbstractMessagingSpanDecorator {
}
@Override
-public String getDestination(Exchange exchange, Endpoint endpoint) {
-Map queryParameters =
toQueryParameters(endpoint.getEndpointUri());
-String topic = queryParameters.get("topic");
-return topic != null ? topic : super.getDestination(exchange,
endpoint);
-}
-
-@Override
protected String getMessageId(Exchange exchange) {
return exchange.getIn().getHeader(NATS_SID, String.class);
}
[camel] branch master updated (199b167 -> 1755297)
This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a change to branch master in repository https://gitbox.apache.org/repos/asf/camel.git. from 199b167 camel-nats - Let producer use byte[] if possible instead of string as first choice new 6f2ad84 CAMEL-14253: camel-nats - Configure brokers on component level new ec71087 Regen new 725fed6 CAMEL-14253: camel-nats - Configure brokers on component level new 1755297 CAMEL-14253: camel-nats - Configure brokers on component level The 4 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: .../camel-nats/src/main/docs/nats-component.adoc | 87 +++--- .../apache/camel/component/nats/NatsComponent.java | 18 +- .../camel/component/nats/NatsConfiguration.java| 20 +-- .../apache/camel/component/nats/NatsConsumer.java | 1 - .../apache/camel/component/nats/NatsEndpoint.java | 6 +- .../apache/camel/component/nats/NatsProducer.java | 1 + .../component/nats/NatsAuthConsumerLoadTest.java | 4 +- .../camel/component/nats/NatsAuthProducerTest.java | 3 +- .../camel/component/nats/NatsAuthTestSupport.java | 13 +- .../nats/NatsAuthTokenConsumerLoadTest.java| 4 +- .../component/nats/NatsAuthTokenProducerTest.java | 3 +- .../component/nats/NatsAuthTokenTestSupport.java | 14 +- .../camel/component/nats/NatsConsumerLoadTest.java | 9 +- .../nats/NatsConsumerMaxMessagesQueueTest.java | 8 +- .../nats/NatsConsumerMaxMessagesTest.java | 5 +- .../component/nats/NatsConsumerReplyToTest.java| 6 +- .../camel/component/nats/NatsConsumerTest.java | 5 +- .../nats/NatsConsumerWithConnectionLoadTest.java | 15 +- .../nats/NatsConsumerWithRedeliveryTest.java | 17 +- .../camel/component/nats/NatsProducerTLSTest.java | 3 +- .../camel/component/nats/NatsProducerTest.java | 3 +- .../camel/component/nats/NatsTestSupport.java | 13 +- .../opentracing/decorators/NatsSpanDecorator.java | 10 -- .../endpoint/dsl/NatsEndpointBuilderFactory.java | 185 ++--- .../modules/ROOT/pages/nats-component.adoc | 107 +--- .../modules/ROOT/pages/rest-swagger-component.adoc | 3 +- .../springboot/NatsComponentConfiguration.java | 13 ++ 27 files changed, 357 insertions(+), 219 deletions(-)
[GitHub] [camel-quarkus] ppalaga commented on a change in pull request #506: feat: base64 extension
ppalaga commented on a change in pull request #506: feat: base64 extension
URL: https://github.com/apache/camel-quarkus/pull/506#discussion_r353613337
##
File path:
integration-tests/base64/src/test/java/org/apache/camel/quarkus/component/base64/it/Base64Test.java
##
@@ -0,0 +1,43 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements. See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.camel.quarkus.component.base64.it;
+
+import io.quarkus.test.junit.QuarkusTest;
+import io.restassured.RestAssured;
+import io.restassured.http.ContentType;
+import io.restassured.response.ExtractableResponse;
+import org.junit.jupiter.api.Assertions;
+import org.junit.jupiter.api.Test;
+
+@QuarkusTest
+class Base64Test {
+
+@Test
+public void test() {
+byte[] body;
+
+ExtractableResponse response = RestAssured.given() //
+.contentType(ContentType.BINARY).body("Hello
World".getBytes()).post("/base64/post") //
Review comment:
String.getBytes() relies on the default encoding of the given platform and
therefore this test will fail on exotic platforms that have some ASCII
incompatible default encoding set.
```suggestion
.contentType(ContentType.BINARY).body("Hello
World".getBytes("UTF-8")).post("/base64/post") //
```
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] [camel-quarkus] lburgazzoli commented on issue #507: Automatically register dozer mapping classes for reflection
lburgazzoli commented on issue #507: Automatically register dozer mapping classes for reflection URL: https://github.com/apache/camel-quarkus/pull/507#issuecomment-561526415 ok to test This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
