activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From clebertsuco...@apache.org
Subject [1/2] activemq-artemis git commit: NO-JIRA removed out of date info regarding jms queue specific config
Date Sat, 19 Aug 2017 16:58:54 GMT
Repository: activemq-artemis
Updated Branches:
  refs/heads/master 27d37b735 -> c54a26da3


NO-JIRA removed out of date info regarding jms queue specific config


Project: http://git-wip-us.apache.org/repos/asf/activemq-artemis/repo
Commit: http://git-wip-us.apache.org/repos/asf/activemq-artemis/commit/a00c8ef9
Tree: http://git-wip-us.apache.org/repos/asf/activemq-artemis/tree/a00c8ef9
Diff: http://git-wip-us.apache.org/repos/asf/activemq-artemis/diff/a00c8ef9

Branch: refs/heads/master
Commit: a00c8ef94a601537e4698fe872b582d592d4abc5
Parents: 27d37b7
Author: Pat Fox <pat.g.fox@gmail.com>
Authored: Sat Aug 19 12:55:28 2017 +0200
Committer: Clebert Suconic <clebertsuconic@apache.org>
Committed: Sat Aug 19 12:58:48 2017 -0400

----------------------------------------------------------------------
 docs/user-manual/en/core-bridges.md | 10 ----------
 1 file changed, 10 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/activemq-artemis/blob/a00c8ef9/docs/user-manual/en/core-bridges.md
----------------------------------------------------------------------
diff --git a/docs/user-manual/en/core-bridges.md b/docs/user-manual/en/core-bridges.md
index 712aa80..79e7906 100644
--- a/docs/user-manual/en/core-bridges.md
+++ b/docs/user-manual/en/core-bridges.md
@@ -80,16 +80,6 @@ Let's take a look at all the parameters in turn:
     The queue must already exist by the time the bridge is instantiated
     at start-up.
 
-    > **Note**
-    >
-    > If you're using JMS then normally the JMS configuration
-    > `activemq-jms.xml` is loaded after the core configuration file
-    > `broker.xml` is loaded. If your bridge is
-    > consuming from a JMS queue then you'll need to make sure the JMS
-    > queue is also deployed as a core queue in the core configuration.
-    > Take a look at the bridge example for an example of how this is
-    > done.
-
 -   `forwarding-address`. This is the address on the target server that
     the message will be forwarded to. If a forwarding address is not
     specified, then the original address of the message will be


Mime
View raw message