svn commit: r1000435 - in /websites/production/camel/content: articles.html cache/main.pageCache
Author: buildbot Date: Thu Nov 3 12:19:55 2016 New Revision: 1000435 Log: Production update by buildbot for camel Modified: websites/production/camel/content/articles.html websites/production/camel/content/cache/main.pageCache Modified: websites/production/camel/content/articles.html == --- websites/production/camel/content/articles.html (original) +++ websites/production/camel/content/articles.html Thu Nov 3 12:19:55 2016 @@ -75,7 +75,7 @@ -See alsoSee also http://camel.apache.org/user-stories.html";>Camel User Stories.If you have never used or seen Camel before, then you should start with http://www.kai-waehner.de/blog/2012/05/04/apache-camel-tutorial-introduction/"; rel="nofollow">Apache Camel Tutorial – Introduction to EIP, Routes, Components, Testing, and other Concepts - an article by Kai Wähner, where he puts EIP and Camel into the big picture and gives a run down of the important Camel concepts. https://github.com/megachucky/camel-infoq"; rel="nofollow">Demo source code can be downloaded at github to get started with your first Camel project easily.Archived Webinars and Screencastshttps://www.youtube.com/watch?v=fxpS9pf6TVk&list=PLUDjw7NbNcoyOyhrIIw9cChAHWdaCxIob&index=17"; rel="nofollow">Apache Camel - The Integration Library - A 50 minute video from September 2016 where Claus Ibsen presents Apache Camel at the JDKIO 2016 conference.https://www.youtube.com/watch?v=jZE-YSHK_gw&sns=tw"; rel="nofollow">Apache Camel First Steps - A 10 minute video from December 2015 where Vivian van Zyl gives a high level overview of Apache Camel and demonstrates how to start using Camel with live code demo.https://www.youtube.com/watch?v=ouJ3SQHnQ6I&feature=youtu.be&a"; rel="nofollow">Fabric8 Camel Microservices for Docker an d Kubernetes - A 55 minute video from http://rigadevday.lv/#/index"; rel="nofollow">Riga Dev Day 2016 conference where Claus Ibsen talks about developing Camel microservices ready for the container platforms.https://www.youtube.com/watch?v=91UiQgazt3g"; rel="nofollow">Developing Microservices with Apache Camel - Video from November 2015 at the MSA Day in New York where Claus Ibsen talks developing Camel based microservices for docker containers running on Kubernetes. http://www.slideshare.net/davsclaus/developing-microservices-with-apache-camel"; rel="nofollow">Slides are here.https://www.youtube.com/watch?v=o8ZRE9DM3Es"; rel="nofollow">Wild Flies and A Camel - Video from Oredev 2015 where Markus Eisele talks about Apache Camel and JBoss Wildfly.https://www.youtube.com/watch?v=nqQaR7vUxfg&index=13&list=PLPIzp-E1msrZz6RNdbDiK0nKuxAUZPs77"; rel="nofollow">JavaOne 2015 Riding a Camel through the JEEHara - Video from JavaOne 2015 where Markus Eisele introduces Apache Camel and how to use it with JEE.https://www.youtube.com/watch?v=jbj1TJ_2XBQ&feature=youtu.be&a"; style="line-height: 1.42857;" rel="nofollow">Apache Camel in the clouds - Video from Devnexus 2015 where Markus Eisele talk about Apache Camel in the clouds running on openshifthttps://vimeo.com/130993910"; rel="nofollow">GeeCON 2015: Markus Eisele - Wild Flies and a Camel - Java EE Integration - Video from GeeCon 2015 where Markus Eisele talks about Apache Camel and how Camel can work with Wildflyhttps://vimeo.com/105743314"; rel="nofollow">Hvordan få en ka mel til å danse (September 2014) by Per Jørgen Walstrøm & Audun Fauchald Strand - (JavaZone 2014) in Norwegianhttp://www.youtube.com/watch?v=_pEwoztbfYI&feature=youtu.be&a"; rel="nofollow">Integration using Apache Camel and Groovy (June 2014) by Claus Ibsen, presenting Camel, Groovy, and http://hawt.io/"; rel="nofollow">hawtio at http://gr8conf.eu/#/"; rel="nofollow">gr8conf 2014.https://skillsmatter.com/skillscasts/5074-effective-system-integrations-with-apache-camel"; rel="nofollow">Effective System Integrations with Apache Camel (March 2014) by Jakub Korabhttp://www.youtube.com/watch?v=lOxUs_JleSs&feature=youtu.be&a"; rel="nofollow">Getting started with Apache Camel video from Barcel onaJUG (January 2014) by Claus Ibsenhttp://vimeo.com/68442425"; rel="nofollow">Camel in the cloud demo from CamelOne 2013 - Video presentation from CamelOne 2013 demonstrating Camel in the cloud using http://fuse.fusesource.org/fabric/"; rel="nofollow">Fuse Fabric and http://hawt.io/"; rel="nofollow">hawtiohttp://javagruppen.dk/index.php/moder/historiske-moder/285-javagruppemode-115-apache-camel-i-aarhus"; rel="nofollow">Getting started with Apache Camel - Video presentation from Javagruppen meeting by Claus Ibsen (May 2013)http://blip.tv/dzone/apache-camel-essential-components-6511579"; rel="nofollow">Apache Camel Essential Components by Christian Posta (January 2013)http://www.youtube.com/watch?v=i_g91CzHgxg"; rel="nofollow">Leverage Enterprise Integration Patterns with Apache Camel and Twitter by Bruno Borges (JavaOne 2012)http://ww
camel git commit: CAMEL-10441 Updated the documentation of WorkerGroup option in camel-netty4
Repository: camel
Updated Branches:
refs/heads/camel-2.18.x 8351873ee -> c5a8c6778
CAMEL-10441 Updated the documentation of WorkerGroup option in camel-netty4
Project: http://git-wip-us.apache.org/repos/asf/camel/repo
Commit: http://git-wip-us.apache.org/repos/asf/camel/commit/c5a8c677
Tree: http://git-wip-us.apache.org/repos/asf/camel/tree/c5a8c677
Diff: http://git-wip-us.apache.org/repos/asf/camel/diff/c5a8c677
Branch: refs/heads/camel-2.18.x
Commit: c5a8c6778a5ebb6fda957427160d57602c0bac3e
Parents: 8351873
Author: Willem Jiang
Authored: Thu Nov 3 18:34:29 2016 +0800
Committer: Willem Jiang
Committed: Thu Nov 3 19:09:59 2016 +0800
--
.../netty4/springboot/NettyComponentConfiguration.java | 5 +++--
.../camel-netty4-http/src/main/docs/netty4-http-component.adoc | 4 ++--
components/camel-netty4/src/main/docs/netty4-component.adoc| 4 ++--
.../component/netty4/NettyServerBootstrapConfiguration.java| 6 +++---
4 files changed, 10 insertions(+), 9 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/camel/blob/c5a8c677/components-starter/camel-netty4-starter/src/main/java/org/apache/camel/component/netty4/springboot/NettyComponentConfiguration.java
--
diff --git
a/components-starter/camel-netty4-starter/src/main/java/org/apache/camel/component/netty4/springboot/NettyComponentConfiguration.java
b/components-starter/camel-netty4-starter/src/main/java/org/apache/camel/component/netty4/springboot/NettyComponentConfiguration.java
index 2c6ffe0..fb5f59d 100644
---
a/components-starter/camel-netty4-starter/src/main/java/org/apache/camel/component/netty4/springboot/NettyComponentConfiguration.java
+++
b/components-starter/camel-netty4-starter/src/main/java/org/apache/camel/component/netty4/springboot/NettyComponentConfiguration.java
@@ -449,8 +449,9 @@ public class NettyComponentConfiguration {
private EventLoopGroup bossGroup;
/**
* To use a explicit EventLoopGroup as the boss thread pool. For
example
- * to share a thread pool with multiple consumers. By default each
- * consumer has their own boss pool with 1 core thread.
+ * to share a thread pool with multiple consumers or producers. By
+ * default each consumer or producer has their own worker pool with 2 x
+ * cpu count core threads.
*/
private EventLoopGroup workerGroup;
/**
http://git-wip-us.apache.org/repos/asf/camel/blob/c5a8c677/components/camel-netty4-http/src/main/docs/netty4-http-component.adoc
--
diff --git
a/components/camel-netty4-http/src/main/docs/netty4-http-component.adoc
b/components/camel-netty4-http/src/main/docs/netty4-http-component.adoc
index 21d994a..b3265bc 100644
--- a/components/camel-netty4-http/src/main/docs/netty4-http-component.adoc
+++ b/components/camel-netty4-http/src/main/docs/netty4-http-component.adoc
@@ -148,8 +148,6 @@ The Netty4 HTTP component supports 82 endpoint options
which are listed below:
| traceEnabled | consumer (advanced) | false | boolean | Specifies whether to
enable HTTP TRACE for this Netty HTTP consumer. By default TRACE is turned off.
| urlDecodeHeaders | consumer (advanced) | false | boolean | If this option is
enabled then during binding from Netty to Camel Message then the header values
will be URL decoded (eg 20 will be a space character. Notice this option is
used by the default org.apache.camel.component.netty.http.NettyHttpBinding and
therefore if you implement a custom
org.apache.camel.component.netty4.http.NettyHttpBinding then you would need to
decode the headers accordingly to this option.
| usingExecutorService | consumer (advanced) | true | boolean | Whether to use
ordered thread pool to ensure events are processed orderly on the same channel.
-| workerCount | consumer (advanced) | | int | When netty works on nio mode it
uses default workerCount parameter from Netty which is cpu_core_threads2. User
can use this operation to override the default workerCount from Netty
-| workerGroup | consumer (advanced) | | EventLoopGroup | To use a explicit
EventLoopGroup as the boss thread pool. For example to share a thread pool with
multiple consumers. By default each consumer has their own boss pool with 1
core thread.
| connectTimeout | producer | 1 | int | Time to wait for a socket
connection to be available. Value is in millis.
| requestTimeout | producer | | long | Allows to use a timeout for the Netty
producer when calling a remote server. By default no timeout is in use. The
value is in milli seconds so eg 3 is 30 seconds. The requestTimeout is
using Netty's ReadTimeoutHandler to trigger the timeout.
| reuseChannel | producer | false | boolean | This option allows
camel git commit: CAMEL-10441 Updated the documentation of WorkerGroup option in camel-netty4
Repository: camel
Updated Branches:
refs/heads/master 9b0b25886 -> 200e097d9
CAMEL-10441 Updated the documentation of WorkerGroup option in camel-netty4
Project: http://git-wip-us.apache.org/repos/asf/camel/repo
Commit: http://git-wip-us.apache.org/repos/asf/camel/commit/200e097d
Tree: http://git-wip-us.apache.org/repos/asf/camel/tree/200e097d
Diff: http://git-wip-us.apache.org/repos/asf/camel/diff/200e097d
Branch: refs/heads/master
Commit: 200e097d9df501724b4e7681768562daef3e4359
Parents: 9b0b258
Author: Willem Jiang
Authored: Thu Nov 3 18:34:29 2016 +0800
Committer: Willem Jiang
Committed: Thu Nov 3 18:34:29 2016 +0800
--
.../netty4/springboot/NettyComponentConfiguration.java | 5 +++--
.../camel-netty4-http/src/main/docs/netty4-http-component.adoc | 4 ++--
components/camel-netty4/src/main/docs/netty4-component.adoc| 4 ++--
.../component/netty4/NettyServerBootstrapConfiguration.java| 6 +++---
4 files changed, 10 insertions(+), 9 deletions(-)
--
http://git-wip-us.apache.org/repos/asf/camel/blob/200e097d/components-starter/camel-netty4-starter/src/main/java/org/apache/camel/component/netty4/springboot/NettyComponentConfiguration.java
--
diff --git
a/components-starter/camel-netty4-starter/src/main/java/org/apache/camel/component/netty4/springboot/NettyComponentConfiguration.java
b/components-starter/camel-netty4-starter/src/main/java/org/apache/camel/component/netty4/springboot/NettyComponentConfiguration.java
index 2c6ffe0..fb5f59d 100644
---
a/components-starter/camel-netty4-starter/src/main/java/org/apache/camel/component/netty4/springboot/NettyComponentConfiguration.java
+++
b/components-starter/camel-netty4-starter/src/main/java/org/apache/camel/component/netty4/springboot/NettyComponentConfiguration.java
@@ -449,8 +449,9 @@ public class NettyComponentConfiguration {
private EventLoopGroup bossGroup;
/**
* To use a explicit EventLoopGroup as the boss thread pool. For
example
- * to share a thread pool with multiple consumers. By default each
- * consumer has their own boss pool with 1 core thread.
+ * to share a thread pool with multiple consumers or producers. By
+ * default each consumer or producer has their own worker pool with 2 x
+ * cpu count core threads.
*/
private EventLoopGroup workerGroup;
/**
http://git-wip-us.apache.org/repos/asf/camel/blob/200e097d/components/camel-netty4-http/src/main/docs/netty4-http-component.adoc
--
diff --git
a/components/camel-netty4-http/src/main/docs/netty4-http-component.adoc
b/components/camel-netty4-http/src/main/docs/netty4-http-component.adoc
index f122836..382e090 100644
--- a/components/camel-netty4-http/src/main/docs/netty4-http-component.adoc
+++ b/components/camel-netty4-http/src/main/docs/netty4-http-component.adoc
@@ -148,8 +148,6 @@ The Netty4 HTTP component supports 83 endpoint options
which are listed below:
| traceEnabled | consumer (advanced) | false | boolean | Specifies whether to
enable HTTP TRACE for this Netty HTTP consumer. By default TRACE is turned off.
| urlDecodeHeaders | consumer (advanced) | false | boolean | If this option is
enabled then during binding from Netty to Camel Message then the header values
will be URL decoded (eg 20 will be a space character. Notice this option is
used by the default org.apache.camel.component.netty.http.NettyHttpBinding and
therefore if you implement a custom
org.apache.camel.component.netty4.http.NettyHttpBinding then you would need to
decode the headers accordingly to this option.
| usingExecutorService | consumer (advanced) | true | boolean | Whether to use
ordered thread pool to ensure events are processed orderly on the same channel.
-| workerCount | consumer (advanced) | | int | When netty works on nio mode it
uses default workerCount parameter from Netty which is cpu_core_threads2. User
can use this operation to override the default workerCount from Netty
-| workerGroup | consumer (advanced) | | EventLoopGroup | To use a explicit
EventLoopGroup as the boss thread pool. For example to share a thread pool with
multiple consumers. By default each consumer has their own boss pool with 1
core thread.
| connectTimeout | producer | 1 | int | Time to wait for a socket
connection to be available. Value is in millis.
| cookieHandler | producer | | CookieHandler | Configure a cookie handler to
maintain a HTTP session
| requestTimeout | producer | | long | Allows to use a timeout for the Netty
producer when calling a remote server. By default no timeout is in use. The
value is in milli seconds so eg 3 is 30 seconds. The requestTimeout is
using Netty's ReadTimeoutHandle
camel git commit: Upgrade RX Java to version 1.2.2
Repository: camel Updated Branches: refs/heads/master 15ad4500c -> 9b0b25886 Upgrade RX Java to version 1.2.2 Project: http://git-wip-us.apache.org/repos/asf/camel/repo Commit: http://git-wip-us.apache.org/repos/asf/camel/commit/9b0b2588 Tree: http://git-wip-us.apache.org/repos/asf/camel/tree/9b0b2588 Diff: http://git-wip-us.apache.org/repos/asf/camel/diff/9b0b2588 Branch: refs/heads/master Commit: 9b0b258860b3128c6cb52ed94641a57ee184a40e Parents: 15ad450 Author: Andrea Cosentino Authored: Thu Nov 3 10:43:05 2016 +0100 Committer: Andrea Cosentino Committed: Thu Nov 3 10:43:05 2016 +0100 -- parent/pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/camel/blob/9b0b2588/parent/pom.xml -- diff --git a/parent/pom.xml b/parent/pom.xml index 2a1c0e1..fcaf23d 100644 --- a/parent/pom.xml +++ b/parent/pom.xml @@ -506,7 +506,7 @@ 2.19.0.Final 1.0_3 1.0 -1.2.1 +1.2.2 1.3.2_2 9.7.0-8_1 9.7.0-8
svn commit: r1000429 - in /websites/production/camel/content: cache/main.pageCache netty4.html
Author: buildbot Date: Thu Nov 3 09:19:22 2016 New Revision: 1000429 Log: Production update by buildbot for camel Modified: websites/production/camel/content/cache/main.pageCache websites/production/camel/content/netty4.html Modified: websites/production/camel/content/cache/main.pageCache == Binary files - no diff available. Modified: websites/production/camel/content/netty4.html == --- websites/production/camel/content/netty4.html (original) +++ websites/production/camel/content/netty4.html Thu Nov 3 09:19:22 2016 @@ -98,7 +98,7 @@ netty4:udp://remotehost:9/[?options] ]]> This component supports producer and consumer endpoints for both TCP and UDP.You can append query options to the URI in the following format, ?option=value&option=value&...Options - NameDefault ValueDescriptionkeepAlivetrueSetting to ensure socket is not closed due to inactivitytcpNoDelaytrueSetting to improve TCP protocol performancebacklog Allows to configure a backlog for netty consumer (server). Note the backlog is just a best effort depending on the OS. Setting this option to a value such as 200, 500 or 1000, tells the TCP stack how long the "accept" queue can be. If this option is not configured, then the backlog depends on OS setting.broadcastfalseSetting to choose Multicast over UDPconnectTimeout1Time to wait for a socket connection to be available. Value is in millis.reuseAddresstrueSetting to facilitate socket multiplexingsynctrueSetting to set endpoint as one-way or request-responsesynchronousfalseBy default, the Asynchronous Routing Engine is used. Set to true to force processing synchronously.sslfalseSetting to specify whether SSL encryption is applied to this endpointsslClientCertHeadersfalseWhen enabled and in SSL mode, then the Netty consumer will enrich the Camel Message with headers having information about the client certificate such as subject name, issuer name, serial number, and the valid date range.sendBufferSize65536 bytesThe TCP/UDP buffer sizes to be used dur ing outbound communication. Size is bytes.receiveBufferSize65536 bytesThe TCP/UDP buffer sizes to be used during inbound communication. Size is bytes.option.XXXnullAllows to configure additional netty options using "option." as prefix. For example "option.child.keepAlive=false" to set the netty option "child.keepAlive=false". See the Netty documentation for possible options that can be used.corePoolSize10The number of allocated threads at component startup. Defaults to 10. Note: This option is removed from Camel 2.9.2 onwards. As we rely on Nettys default settings.maxPoolSize100The maximum number of threads that may be allocated to this endpoint. Defaults to 100. Note: This option is removed from Camel 2.9.2 onwards. As we rely on Nettys default settings.disconnectfalseWhether or not to disconnect(close) from Netty Channel right after use. Can be used for bo th consumer and producer.lazyChannelCreationtrueChannels can be lazily created to avoid exceptions, if the remote server is not up and running when the Camel producer is started.transferExchangefalseOnly used for TCP. You can transfer the exchange over the wire instead of just the body. The following fields are transferred: In body, Out body, fault body, In headers, Out headers, fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level.< /p>allowSerializedHeadersfalseCamel 2.18 Only used for TCP when transferExchange is true. Serializable objects in In/Out headers and exchange properties are transfered.disconnectOnNoReplytrueIf sync is enabled then this option dictates NettyConsumer if it should disconnect where there is no reply to send back.noReplyLogLevelWARNIf sync is enabled this option dictates NettyConsumer which logging level to use when logging a there is no reply to send back. Values are: FATAL, ERROR, INFO, DEBUG, OFF.serverExceptionCaughtLogLevelWARNIf the server (NettyConsumer) catches an exception then its logged using this logging level.serverClosedChannelExceptionCaughtLogLevelDEBUGIf the server (NettyConsumer) catches an java.nio.channels.ClosedChannelException then its logged using this logging level. This is used to avoid logging the closed channel excepti ons, as clients can disconnect abruptly and then cause a flod of closed exceptions in the Netty server.allowDefaultCodectrueThe netty component installs a default codec if both, encoder/deocder is null and textline is false. Setting allowDefaultCodec to false prevents the netty component from installing a default codec as the first element in the filter chain.textlinefalseOnly used for TCP. If no codec is specified, you can use this flag to indicate a text line based codec; if not
[2/2] camel git commit: Upgrade Kubernetes/Openshift client to version 1.4.18
Upgrade Kubernetes/Openshift client to version 1.4.18 Project: http://git-wip-us.apache.org/repos/asf/camel/repo Commit: http://git-wip-us.apache.org/repos/asf/camel/commit/15ad4500 Tree: http://git-wip-us.apache.org/repos/asf/camel/tree/15ad4500 Diff: http://git-wip-us.apache.org/repos/asf/camel/diff/15ad4500 Branch: refs/heads/master Commit: 15ad4500c1b642f9cee9d6548db72d4d0368e125 Parents: aa91edd Author: Andrea Cosentino Authored: Thu Nov 3 08:18:32 2016 +0100 Committer: Andrea Cosentino Committed: Thu Nov 3 08:18:32 2016 +0100 -- parent/pom.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) -- http://git-wip-us.apache.org/repos/asf/camel/blob/15ad4500/parent/pom.xml -- diff --git a/parent/pom.xml b/parent/pom.xml index 0ce60e7..2a1c0e1 100644 --- a/parent/pom.xml +++ b/parent/pom.xml @@ -380,7 +380,7 @@ 4.0.7 6.4.0.Final 0.4.9 -1.4.17 +1.4.18 1.0.63 2.3.0_3 1.8 @@ -467,7 +467,7 @@ 6.8.2 2.4.1 2.7.0.Final -1.4.17 +1.4.18 6.4.0.Final 2.0.8_6 2.4_5
[1/2] camel git commit: Upgrade Kubernetes-model to version 1.0.63
Repository: camel Updated Branches: refs/heads/master 210502e22 -> 15ad4500c Upgrade Kubernetes-model to version 1.0.63 Project: http://git-wip-us.apache.org/repos/asf/camel/repo Commit: http://git-wip-us.apache.org/repos/asf/camel/commit/aa91edd2 Tree: http://git-wip-us.apache.org/repos/asf/camel/tree/aa91edd2 Diff: http://git-wip-us.apache.org/repos/asf/camel/diff/aa91edd2 Branch: refs/heads/master Commit: aa91edd23490ddbb628b2f62522532ccc1ddb655 Parents: 210502e Author: Andrea Cosentino Authored: Thu Nov 3 08:14:57 2016 +0100 Committer: Andrea Cosentino Committed: Thu Nov 3 08:14:57 2016 +0100 -- parent/pom.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/camel/blob/aa91edd2/parent/pom.xml -- diff --git a/parent/pom.xml b/parent/pom.xml index 9830a4a..0ce60e7 100644 --- a/parent/pom.xml +++ b/parent/pom.xml @@ -381,7 +381,7 @@ 6.4.0.Final 0.4.9 1.4.17 -1.0.61 +1.0.63 2.3.0_3 1.8 7.6.0
