activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [4/5] activemq-6 git commit: adding wording about Camel
Date Fri, 27 Feb 2015 10:42:41 GMT
adding wording about Camel


Branch: refs/heads/master
Commit: b1c8ff3e49cc26554228d2c1d0e5c2890630dd6f
Parents: 6f9c4df
Author: Clebert Suconic <>
Authored: Thu Feb 26 22:41:37 2015 -0500
Committer: Clebert Suconic <>
Committed: Thu Feb 26 23:19:48 2015 -0500

 docs/user-manual/en/ | 4 ++++
 1 file changed, 4 insertions(+)
diff --git a/docs/user-manual/en/ b/docs/user-manual/en/
index 7ee1d06..6c0c0ec 100644
--- a/docs/user-manual/en/
+++ b/docs/user-manual/en/
@@ -6,6 +6,10 @@ The function of the bridge is to consume messages from a source queue or
 topic, and send them to a target queue or topic, typically on a
 different server.
+> *Notice:*
+> The JMS Bridge is not intended as a replacement for transformation and more expert systems
such as Camel.
+> The JMS Bridge may be useful for fast transfers as this chapter covers, but keep in
mind that more complex scenarios requiring transformations will require you to use a more
advanced transformation system that will play on use cases that will go beyond ActiveMQ.
 The source and target servers do not have to be in the same cluster
 which makes bridging suitable for reliably sending messages from one
 cluster to another, for instance across a WAN, and where the connection

View raw message