You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by da...@apache.org on 2019/11/22 15:14:29 UTC
[camel] branch master updated (3c8594b -> 1d123ec)
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 3c8594b Revert "Revert "CAMEL-14146 : camel-hdfs - Consumer that splits with ChunkSize should add similar header info like the Splitter (#3354)" (#3359)"
new c0e4970 CAMEL-14191: EIP docs - Add links to last EIP patterns and add new pages if missing content
new 866c3d1 Regen
new 1d123ec CAMEL-14191: EIP docs - Add links to last EIP patterns and add new pages if missing content
The 3 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:
.../modules/ROOT/pages/netty-http-component.adoc | 3 ++-
.../ROOT/assets/images/eip/MessageBroker.gif | Bin 0 -> 1686 bytes
.../ROOT/assets/images/eip/MessageBrokerIcon.gif | Bin 0 -> 547 bytes
.../ROOT/assets/images/eip/ProcessManager.gif | Bin 0 -> 3175 bytes
.../ROOT/assets/images/eip/ProcessManagerIcon.gif | Bin 0 -> 429 bytes
.../pages/enterprise-integration-patterns.adoc | 10 +++++++++
.../modules/ROOT/pages/message-broker.adoc | 20 +++++++++++++++++
.../modules/ROOT/pages/process-manager.adoc | 25 +++++++++++++++++++++
8 files changed, 57 insertions(+), 1 deletion(-)
create mode 100644 docs/user-manual/modules/ROOT/assets/images/eip/MessageBroker.gif
create mode 100644 docs/user-manual/modules/ROOT/assets/images/eip/MessageBrokerIcon.gif
create mode 100644 docs/user-manual/modules/ROOT/assets/images/eip/ProcessManager.gif
create mode 100644 docs/user-manual/modules/ROOT/assets/images/eip/ProcessManagerIcon.gif
create mode 100644 docs/user-manual/modules/ROOT/pages/message-broker.adoc
create mode 100644 docs/user-manual/modules/ROOT/pages/process-manager.adoc
[camel] 02/03: Regen
Posted by da...@apache.org.
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 866c3d181a292c223aacb60b65b5e5942e267612
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Fri Nov 22 15:38:01 2019 +0100
Regen
---
docs/components/modules/ROOT/pages/netty-http-component.adoc | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/docs/components/modules/ROOT/pages/netty-http-component.adoc b/docs/components/modules/ROOT/pages/netty-http-component.adoc
index c140ea6..b882de2 100644
--- a/docs/components/modules/ROOT/pages/netty-http-component.adoc
+++ b/docs/components/modules/ROOT/pages/netty-http-component.adoc
@@ -145,7 +145,7 @@ with the following path and query parameters:
|===
-=== Query Parameters (79 parameters):
+=== Query Parameters (80 parameters):
[width="100%",cols="2,5,^1,2",options="header"]
@@ -168,6 +168,7 @@ with the following path and query parameters:
| *compression* (consumer) | Allow using gzip/deflate for compression on the Netty HTTP server if the client supports it from the HTTP headers. | false | boolean
| *disconnectOnNoReply* (consumer) | If sync is enabled then this option dictates NettyConsumer if it should disconnect where there is no reply to send back. | true | boolean
| *httpMethodRestrict* (consumer) | To disable HTTP methods on the Netty HTTP consumer. You can specify multiple separated by comma. | | String
+| *logWarnOnBadRequest* (consumer) | Whether Netty HTTP server should log a WARN if decoding the HTTP request failed and a HTTP Status 400 (bad request) is returned. | true | boolean
| *mapHeaders* (consumer) | If this option is enabled, then during binding from Netty to Camel Message then the headers will be mapped as well (eg added as header to the Camel Message as well). You can turn off this option to disable this. The headers can still be accessed from the org.apache.camel.component.netty.http.NettyHttpMessage message with the method getHttpRequest() that returns the Netty HTTP request io.netty.handler.codec.http.HttpRequest instance. | true | boolean
| *maxHeaderSize* (consumer) | The maximum length of all headers. If the sum of the length of each header exceeds this value, a io.netty.handler.codec.TooLongFrameException will be raised. | 8192 | int
| *nettyServerBootstrapFactory* (consumer) | To use a custom NettyServerBootstrapFactory | | NettyServerBootstrapFactory
[camel] 03/03: CAMEL-14191: EIP docs - Add links to last EIP
patterns and add new pages if missing content
Posted by da...@apache.org.
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 1d123ec43996bda713dc928f074ffd56e0315665
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Fri Nov 22 15:51:26 2019 +0100
CAMEL-14191: EIP docs - Add links to last EIP patterns and add new pages if missing content
---
.../ROOT/assets/images/eip/MessageBroker.gif | Bin 0 -> 1686 bytes
.../ROOT/assets/images/eip/MessageBrokerIcon.gif | Bin 0 -> 547 bytes
.../ROOT/pages/enterprise-integration-patterns.adoc | 5 +++++
.../modules/ROOT/pages/message-broker.adoc | 20 ++++++++++++++++++++
4 files changed, 25 insertions(+)
diff --git a/docs/user-manual/modules/ROOT/assets/images/eip/MessageBroker.gif b/docs/user-manual/modules/ROOT/assets/images/eip/MessageBroker.gif
new file mode 100644
index 0000000..3ddef7b
Binary files /dev/null and b/docs/user-manual/modules/ROOT/assets/images/eip/MessageBroker.gif differ
diff --git a/docs/user-manual/modules/ROOT/assets/images/eip/MessageBrokerIcon.gif b/docs/user-manual/modules/ROOT/assets/images/eip/MessageBrokerIcon.gif
new file mode 100644
index 0000000..e97a88e
Binary files /dev/null and b/docs/user-manual/modules/ROOT/assets/images/eip/MessageBrokerIcon.gif differ
diff --git a/docs/user-manual/modules/ROOT/pages/enterprise-integration-patterns.adoc b/docs/user-manual/modules/ROOT/pages/enterprise-integration-patterns.adoc
index cef0080..53faf62 100644
--- a/docs/user-manual/modules/ROOT/pages/enterprise-integration-patterns.adoc
+++ b/docs/user-manual/modules/ROOT/pages/enterprise-integration-patterns.adoc
@@ -168,6 +168,11 @@ a|image::eip/ProcessManagerIcon.gif[image]
through multiple processing steps when the required steps may not be known
at design-time and may not be sequential?
+a|image::eip/MessageBrokerIcon.gif[image]
+|xref:message-broker.adoc[Message Broker] |How can you decouple the
+destination of a message from the sender and maintain central control
+over the flow of messages?
+
|
|xref:throttle-eip.adoc[Throttler] |How can I throttle messages to ensure
that a specific endpoint does not get overloaded, or we don't exceed an
diff --git a/docs/user-manual/modules/ROOT/pages/message-broker.adoc b/docs/user-manual/modules/ROOT/pages/message-broker.adoc
new file mode 100644
index 0000000..9f101e7
--- /dev/null
+++ b/docs/user-manual/modules/ROOT/pages/message-broker.adoc
@@ -0,0 +1,20 @@
+[[Message-Broker]]
+= Message Broker
+
+Camel supports the
+https://www.enterpriseintegrationpatterns.com/patterns/messaging/MessageBroker.html[Message Broker]
+from the xref:enterprise-integration-patterns.adoc[EIP patterns] book.
+
+How can you decouple the destination of a message from the sender and maintain central control over the flow of messages?
+
+image::eip/MessageBroker.gif[image]
+
+Use a central Message Broker that can receive messages from multiple destinations,
+determine the correct destination and route the message to the correct channel.
+
+Camel supports integration with existing message broker systems such as Apache ActiveMQ,
+Apache Kafka, RabbitMQ, and cloud queue systems such as AWS SQS, and others.
+
+These Camel components allows to both send and receive data from message brokers.
+
+
[camel] 01/03: CAMEL-14191: EIP docs - Add links to last EIP
patterns and add new pages if missing content
Posted by da...@apache.org.
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 c0e49706359935547c5c5e186cbd74ad246d0738
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Fri Nov 22 15:37:56 2019 +0100
CAMEL-14191: EIP docs - Add links to last EIP patterns and add new pages if missing content
---
.../ROOT/assets/images/eip/ProcessManager.gif | Bin 0 -> 3175 bytes
.../ROOT/assets/images/eip/ProcessManagerIcon.gif | Bin 0 -> 429 bytes
.../pages/enterprise-integration-patterns.adoc | 5 +++++
.../modules/ROOT/pages/process-manager.adoc | 25 +++++++++++++++++++++
4 files changed, 30 insertions(+)
diff --git a/docs/user-manual/modules/ROOT/assets/images/eip/ProcessManager.gif b/docs/user-manual/modules/ROOT/assets/images/eip/ProcessManager.gif
new file mode 100644
index 0000000..22c8501
Binary files /dev/null and b/docs/user-manual/modules/ROOT/assets/images/eip/ProcessManager.gif differ
diff --git a/docs/user-manual/modules/ROOT/assets/images/eip/ProcessManagerIcon.gif b/docs/user-manual/modules/ROOT/assets/images/eip/ProcessManagerIcon.gif
new file mode 100644
index 0000000..b1f931d
Binary files /dev/null and b/docs/user-manual/modules/ROOT/assets/images/eip/ProcessManagerIcon.gif differ
diff --git a/docs/user-manual/modules/ROOT/pages/enterprise-integration-patterns.adoc b/docs/user-manual/modules/ROOT/pages/enterprise-integration-patterns.adoc
index 8174f59..cef0080 100644
--- a/docs/user-manual/modules/ROOT/pages/enterprise-integration-patterns.adoc
+++ b/docs/user-manual/modules/ROOT/pages/enterprise-integration-patterns.adoc
@@ -163,6 +163,11 @@ a|image::eip/RoutingTableIcon.gif[image]
consecutively through a series of processing steps when the sequence of
steps is not known at design-time and may vary for each message?
+a|image::eip/ProcessManagerIcon.gif[image]
+|xref:process-manager.adoc[Process Manager] |How do we route a message
+through multiple processing steps when the required steps may not be known
+at design-time and may not be sequential?
+
|
|xref:throttle-eip.adoc[Throttler] |How can I throttle messages to ensure
that a specific endpoint does not get overloaded, or we don't exceed an
diff --git a/docs/user-manual/modules/ROOT/pages/process-manager.adoc b/docs/user-manual/modules/ROOT/pages/process-manager.adoc
new file mode 100644
index 0000000..e22086d
--- /dev/null
+++ b/docs/user-manual/modules/ROOT/pages/process-manager.adoc
@@ -0,0 +1,25 @@
+[[Process-Manager]]
+= Process Manager
+
+Camel supports the
+https://www.enterpriseintegrationpatterns.com/patterns/messaging/ProcessManager.html[Process Manager]
+from the xref:enterprise-integration-patterns.adoc[EIP patterns] book.
+
+The xref:routingSlip-eip.adoc[Routing Slip] demonstrates how a message can be routed through a dynamic series of processing steps.
+The solution of the Routing Slip is based on two key assumptions: the sequence of processing steps has
+to be determined up-front and the sequence is linear. In many cases, these assumptions may not be fulfilled.
+For example, routing decisions might have to be made based on intermediate results.
+Or, the processing steps may not be sequential, but multiple steps might be executed in parallel.
+
+How do we route a message through multiple processing steps when the required steps may not be known
+at design-time and may not be sequential?
+
+image::eip/ProcessManager.gif[image]
+
+Use a central processing unit, a Process Manager, to maintain the state of the sequence and determine
+the next processing step based on intermediate results.
+
+With Camel this pattern is implemented by using the xref:dynamicRouter-eip.adoc[Dynamic Router] pattern.
+Camel's implementation of the dynamic router maintains the state of the sequence, and allows
+to determine the next processing step based dynamically.
+