You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by ac...@apache.org on 2017/11/16 11:52:59 UTC
[camel] branch master updated (ade3159 -> 323bfbb)
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 ade3159 camel-jackson*: JacksonMarshalDateTimezoneTest: force tests to be run with the junit 4 runner, so assumptions work when test is run by maven
new 1d8c36d Upgrade Jackrabbit to version 2.15.8
new 323bfbb Added wiretap EIP 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:
camel-core/src/main/docs/eips/wireTap-eip.adoc | 213 +++++++++++++++++++++++++
parent/pom.xml | 2 +-
2 files changed, 214 insertions(+), 1 deletion(-)
create mode 100644 camel-core/src/main/docs/eips/wireTap-eip.adoc
--
To stop receiving notification emails like this one, please contact
['"commits@camel.apache.org" <co...@camel.apache.org>'].
[camel] 02/02: Added wiretap EIP docs
Posted by ac...@apache.org.
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 323bfbbdd6bb12610adeae71c0bfa645b74a09aa
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Thu Nov 16 12:52:31 2017 +0100
Added wiretap EIP docs
---
camel-core/src/main/docs/eips/wireTap-eip.adoc | 213 +++++++++++++++++++++++++
1 file changed, 213 insertions(+)
diff --git a/camel-core/src/main/docs/eips/wireTap-eip.adoc b/camel-core/src/main/docs/eips/wireTap-eip.adoc
new file mode 100644
index 0000000..56ec216
--- /dev/null
+++ b/camel-core/src/main/docs/eips/wireTap-eip.adoc
@@ -0,0 +1,213 @@
+== Wire Tap EIP
+
+http://www.enterpriseintegrationpatterns.com/WireTap.html[Wire Tap]
+(from the link:enterprise-integration-patterns.html[EIP patterns])
+allows you to route messages to a separate location while they are being
+forwarded to the ultimate destination.
+
+image:http://www.enterpriseintegrationpatterns.com/img/WireTap.gif[image]
+
+=== Streams
+
+If you link:wire-tap.html[Wire Tap] a stream message body then you
+should consider enabling link:stream-caching.html[Stream caching] to
+ensure the message body can be read at each endpoint. See more details
+at link:stream-caching.html[Stream caching].
+
+=== Options
+
+// eip options: START
+The Wire Tap EIP supports 10 options which are listed below:
+
+
+[width="100%",cols="2,5,^1,2",options="header"]
+|===
+| Name | Description | Default | Type
+| *processorRef* | Reference to a Processor to use for creating a new body as the message to use for wire tapping | | String
+| *body* | Uses the expression for creating a new body as the message to use for wire tapping | | NamespaceAware Expression
+| *executorServiceRef* | Uses a custom thread pool | | String
+| *copy* | Uses a copy of the original exchange | true | Boolean
+| *dynamicUri* | Whether the uri is dynamic or static. If the uri is dynamic then the simple language is used to evaluate a dynamic uri to use as the wire-tap destination for each incoming message. This works similar to how the toD EIP pattern works. If static then the uri is used as-is as the wire-tap destination. | true | Boolean
+| *onPrepareRef* | Uses the Processor when preparing the org.apache.camel.Exchange to be send. This can be used to deep-clone messages that should be send or any custom logic needed before the exchange is send. | | String
+| *uri* | *Required* The uri of the endpoint to send to. The uri can be dynamic computed using the org.apache.camel.language.simple.SimpleLanguage expression. | | String
+| *pattern* | Sets the optional ExchangePattern used to invoke this endpoint | | ExchangePattern
+| *cacheSize* | Sets the maximum size used by the org.apache.camel.impl.ConsumerCache which is used to cache and reuse producers. | | Integer
+| *ignoreInvalidEndpoint* | Ignore the invalidate endpoint exception when try to create a producer with that endpoint | false | Boolean
+|===
+// eip options: END
+
+=== WireTap Thread pool
+
+The WireTap uses a thread pool to process the
+tapped messages. This thread pool will by default use the settings
+detailed at link:threading-model.html[Threading Model]. In particular,
+when the pool is exhausted (with all threads utilized), further wiretaps
+will be executed synchronously by the calling thread. To remedy this,
+you can configure an explicit thread pool on the link:wire-tap.html[Wire
+Tap] having either a different rejection policy, a larger worker queue,
+or more worker threads.
+
+=== WireTap Node
+
+Camel's Wire Tap node supports two flavors when tapping an
+link:exchange.html[Exchange]:
+
+- With the traditional Wire Tap, Camel will copy the original
+link:exchange.html[Exchange] and set its
+link:exchange-pattern.html[Exchange Pattern] to *`InOnly`*, as we want
+the tapped link:exchange.html[Exchange] to be sent in a fire and forget
+style. The tapped link:exchange.html[Exchange] is then sent in a
+separate thread so it can run in parallel with the original. Beware that
+only the Exchange is copied - Wire Tap won't do a deep clone (unless you
+specify a custom processor via *`onPrepareRef`* which does that). So all
+copies could share objects from the original Exchange.
+- Camel also provides an option of sending a new
+link:exchange.html[Exchange] allowing you to populate it with new
+values.
+
+=== Sending a Copy (traditional wiretap)
+
+* Using the link:fluent-builders.html[Fluent
+Builders]
+
+[source,java]
+----
+ protected RouteBuilder createRouteBuilder() {
+ return new RouteBuilder() {
+ public void configure() {
+ // START SNIPPET: e1
+ from("direct:start")
+ .to("log:foo")
+ .wireTap("direct:tap")
+ .to("mock:result");
+ // END SNIPPET: e1
+
+ from("direct:tap")
+ .delay(1000).setBody().constant("Tapped")
+ .to("mock:result", "mock:tap");
+
+ from("direct:test").wireTap("direct:a").id("wiretap_1").to("mock:a");
+ from("direct:a").to("mock:b");
+ }
+ };
+ }
+----
+
+=== Sending a New link:exchange.html[Exchange]
+
+*Using the link:fluent-builders.html[Fluent Builders]*
+ Camel supports either a processor or an
+link:expression.html[Expression] to populate the new
+link:exchange.html[Exchange]. Using a processor gives you full power
+over how the link:exchange.html[Exchange] is populated as you can set
+properties, headers, etc. An link:expression.html[Expression] can only
+be used to set the *`IN`* body.
+
+From *Camel 2.3*: the link:expression.html[Expression] or
+link:processor.html[Processor] is pre-populated with a copy of the
+original link:exchange.html[Exchange], which allows you to access the
+original message when you prepare a new link:exchange.html[Exchange] to
+be sent. You can use the *`copy`* option (enabled by default) to
+indicate whether you want this. If you set *`copy=false`*, then it works
+as in *Camel 2.2* or older where the link:exchange.html[Exchange] will
+be empty.
+
+Below is the processor variation. This example is from *Camel 2.3*,
+where we disable *`copy`* by passing in *`false`* to create a new, empty
+link:exchange.html[Exchange]
+
+[source,java]
+----
+ public void testFireAndForgetUsingProcessor() throws Exception {
+ context.addRoutes(new RouteBuilder() {
+ @SuppressWarnings("deprecation")
+ @Override
+ public void configure() throws Exception {
+ // START SNIPPET: e1
+ from("direct:start")
+ .wireTap("direct:foo", false, new Processor() {
+ public void process(Exchange exchange) throws Exception {
+ exchange.getIn().setBody("Bye World");
+ exchange.getIn().setHeader("foo", "bar");
+ }
+ }).to("mock:result");
+
+
+ from("direct:foo").to("mock:foo");
+ // END SNIPPET: e1
+ }
+ });
+ }
+----
+
+
+=== Using Dynamic URIs
+
+*Available as of Camel 2.16:*
+
+For example to wire tap to a dynamic URI, then it supports the same
+dynamic URIs as documented in link:message-endpoint.html[Message
+Endpoint]. For example to wire tap to a JMS queue where the header ID is
+part of the queue name:
+
+[source,java]
+----
+ from("direct:start") .wireTap("jms:queue:backup-$\{header.id}")
+ .to("bean:doSomething");
+----
+
+=== Sending a New exchange and Set Headers in DSL
+
+*Available as of Camel 2.8*
+
+If you send a new message using link:wire-tap.html[Wire Tap], then you
+could only set the message body using an
+link:expression.html[Expression] from the DSL. If you also need to set
+headers, you would have to use a link:processor.html[Processor]. From
+*Camel 2.8*: it's possible to set headers as well using the DSL.
+
+The following example sends a new message which has
+
+* *`Bye World`* as message body.
+* A header with key *`id`* with the value *`123`*.
+* A header with key *`date`* which has current date as value.
+
+=== Java DSL
+
+[source,java]
+----
+ @Override
+ protected RouteBuilder createRouteBuilder() throws Exception {
+ return new RouteBuilder() {
+ @Override
+ public void configure() throws Exception {
+ // START SNIPPET: e1
+ from("direct:start")
+ // tap a new message and send it to direct:tap
+ // the new message should be Bye World with 2 headers
+ .wireTap("direct:tap")
+ // create the new tap message body and headers
+ .newExchangeBody(constant("Bye World"))
+ .newExchangeHeader("id", constant(123))
+ .newExchangeHeader("date", simple("${date:now:yyyyMMdd}"))
+ .end()
+ // here we continue routing the original messages
+ .to("mock:result");
+
+ // this is the tapped route
+ from("direct:tap")
+ .to("mock:tap");
+ // END SNIPPET: e1
+ }
+ };
+ }
+
+----
+
+=== Using `onPrepare` to Execute Custom Logic when Preparing Messages
+
+*Available as of Camel 2.8*
+
+See details at link:multicast.html[Multicast]
+
+link:using-this-pattern.html[Using This Pattern]
--
To stop receiving notification emails like this one, please contact
"commits@camel.apache.org" <co...@camel.apache.org>.
[camel] 01/02: Upgrade Jackrabbit to version 2.15.8
Posted by ac...@apache.org.
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 1d8c36de2bc8705792d43c6c84712cf800590690
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Thu Nov 16 09:08:27 2017 +0100
Upgrade Jackrabbit to version 2.15.8
---
parent/pom.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/parent/pom.xml b/parent/pom.xml
index 64187fd..4ceb9dd 100644
--- a/parent/pom.xml
+++ b/parent/pom.xml
@@ -329,7 +329,7 @@
<jackson2-scala-version>2.6.1</jackson2-scala-version>
<!-- jackson 2.9.x is not yet working with all camel components such as swagger-java -->
<jackson2-version>2.8.10</jackson2-version>
- <jackrabbit-version>2.15.7</jackrabbit-version>
+ <jackrabbit-version>2.15.8</jackrabbit-version>
<jackrabbit-guava-version>15.0</jackrabbit-guava-version>
<jain-sip-ri-bundle-version>1.2.154_2</jain-sip-ri-bundle-version>
<jasn1-version>1.8.2</jasn1-version>
--
To stop receiving notification emails like this one, please contact
"commits@camel.apache.org" <co...@camel.apache.org>.