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
The following commit(s) were added to refs/heads/master by this push:
new 123434e Migration guide: Improve NOTE section
123434e is described below
commit 123434e3e00f2e6146fa4142998dacd1b1dbe75b
Author: Andrea Cosentino <anco...@gmail.com>
AuthorDate: Fri Jan 17 08:57:17 2020 +0100
Migration guide: Improve NOTE section
---
docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide.adoc | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide.adoc
b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide.adoc
index 4ebef1c..acec046 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide.adoc
@@ -27,7 +27,10 @@ This means that the bean is created or looked up once and
reused.
The option `cache` has been deprecated in favour of the new `scope` option
that by default is `Singleton`. You can set this to `Prototype` to use the old
behaviour.
-NOTE: Setting this to Prototype will let Camel create/lookup a new bean
instance, per use; which acts as prototype scoped. However beware that if you
lookup the bean, then the registry that holds the bean, would return a bean
accordingly to its configuration, which can be singleton or prototype scoped.
For example if you use Spring, or CDI, which has their own settings for setting
bean scopes.
+[NOTE]
+====
+Setting this to Prototype will let Camel create/lookup a new bean instance,
per use; which acts as prototype scoped. However beware that if you lookup the
bean, then the registry that holds the bean, would return a bean accordingly to
its configuration, which can be singleton or prototype scoped. For example if
you use Spring, or CDI, which has their own settings for setting bean scopes.
+====
=== camel-irc
