[camel] 03/03: CAMEL-14033: Update doc to say queues should be used for request/response.

[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 4f85af176bd2b0c790f9d8e61c35e006e761ad8c
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Fri Oct 4 08:50:51 2019 +0200

    CAMEL-14033: Update doc to say queues should be used for request/response.
---
 components/camel-sjms/src/main/docs/sjms-batch-component.adoc | 2 --
 components/camel-sjms/src/main/docs/sjms-component.adoc       | 4 ++--
 2 files changed, 2 insertions(+), 4 deletions(-)

diff --git a/components/camel-sjms/src/main/docs/sjms-batch-component.adoc b/components/camel-sjms/src/main/docs/sjms-batch-component.adoc
index 07c3497..371b05d 100644
--- a/components/camel-sjms/src/main/docs/sjms-batch-component.adoc
+++ b/components/camel-sjms/src/main/docs/sjms-batch-component.adoc
@@ -1,8 +1,6 @@
 [[sjms-batch-component]]
 = Simple JMS Batch Component
 
-*Available as of Camel version 2.16*
-
 SJMS Batch is a specialized component for highly performant,
 transactional batch consumption from a JMS queue. It can be thought of
 as a hybrid of a consumer-only component and an
diff --git a/components/camel-sjms/src/main/docs/sjms-component.adoc b/components/camel-sjms/src/main/docs/sjms-component.adoc
index ea633be..f3bc0bb 100644
--- a/components/camel-sjms/src/main/docs/sjms-component.adoc
+++ b/components/camel-sjms/src/main/docs/sjms-component.adoc
@@ -1,8 +1,6 @@
 [[sjms-component]]
 = Simple JMS Component
 
-*Available as of Camel version 2.11*
-
 The Simple JMS Component, or SJMS, is a JMS client for use with Camel
 that uses well known best practices when it comes to JMS client creation
 and configuration. SJMS contains a brand new JMS client API written
@@ -563,6 +561,8 @@ reducing the overhead on the broker since all the messages are consumed
 from the destination in the order they are produced by the interested
 consumer.
 
+NOTE: You should only use queues as destination types, topics is not recommended or fully supported.
+
 Currently the only correlation strategy is to use the `JMSCorrelationId`.
 The _InOut_ Consumer uses this strategy as well ensuring that all
 responses messages to the included `JMSReplyTo` destination also have the