[camel] 02/02: The Camel 3.8 Upgrade guide contained two sections for the camel-infinispan component. Remove the less detailed one.

[pa...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

pascalschumacher pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git

commit 01f1d4865948f50108a7eedb71ddbfbe5ac6711a
Author: PascalSchumacher <pa...@gmx.net>
AuthorDate: Wed Feb 3 21:10:47 2021 +0100

    The Camel 3.8 Upgrade guide contained two sections for the camel-infinispan component. Remove the less detailed one.
---
 .../user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_8.adoc | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_8.adoc b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_8.adoc
index 68343e9..49ec4f2 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_8.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_8.adoc
@@ -63,13 +63,6 @@ not ideal for LRU caches assuming ordering.
 The implementation is not needed anymore in Camel 3, as we are using a simpler default implementation internally.
 This component was deprecated, and has been removed as Maven dependency in `camel-core` pom.xml file.
 
-=== camel-infinispan
-
-The infinispan component has been splitup into client and embedded server mode.
-The module `camel-infinispan` is the client mode, and `camel-infinispan-embedded` is for server mode.
-Most use cases would be client mode to integrate with an existing Infinispan cluster, therefore it was choosen
-to be the `camel-infinispan` component.
-
 === camel-activemq and camel-jms
 
 The JMS and ActiveMQ components now support the optimized toD EIP pattern by using a single endpoint/producer for dynamic destination names.