This is an automated email from the ASF dual-hosted git repository.
aldettinger 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 19376f2 Fixed typos
19376f2 is described below
commit 19376f23fb908c24aa1c43589218525d36b1a711
Author: aldettinger <aldettin...@gmail.com>
AuthorDate: Wed Jan 22 12:33:14 2020 +0100
Fixed typos
---
.../ROOT/pages/pluggable-class-resolvers.adoc | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/docs/user-manual/modules/ROOT/pages/pluggable-class-resolvers.adoc
b/docs/user-manual/modules/ROOT/pages/pluggable-class-resolvers.adoc
index 39c8251..81cc1d0 100644
--- a/docs/user-manual/modules/ROOT/pages/pluggable-class-resolvers.adoc
+++ b/docs/user-manual/modules/ROOT/pages/pluggable-class-resolvers.adoc
@@ -1,13 +1,13 @@
= Pluggable Class Resolvers
Camel provides pluggable class resolvers allowing third party platforms
-and contains to provide their own resolvers in case the default ones
-does not work on their platform. For example we provide a
-`WebSpherePackageScanClassResolver` out of the box in Camel to
-integration Camel with IBM WebSphere.
+and containers to provide their own resolvers in case the default ones
+would not fit. For example we provide a
+`WebSpherePackageScanClassResolver` out of the box to
+integrate Camel with IBM WebSphere.
Platform providers should look in the `org.apache.camel.spi` package for
-the following pluggble resolvers:
+the pluggable resolvers below:
* `PackageScanClassResolver`
* `ClassResolver`
@@ -18,10 +18,10 @@ run in any OSGi container.
== Configuration of a custom class resolver
-To instruct Camel to use your own custom class resolver you set the
+To instruct Camel to use your own custom class resolver, you set the
resolver on the `CamelContext` using the appropriate setters.
-== Easy configuration in Spring XML
+== Easy configuration of a custom class resolver in Spring XML
We have provided easy configuration in Spring XML as you just need to
declare a spring bean with your custom resolver and Camel will pick it
@@ -42,17 +42,17 @@ up automatically.
In the sample above the CamelContext will automatic detect the
`jbossresolver` bean and use it instead of its default one.
-== FactoryFinderResolver
+== Configuration of a custom factory finder resolver
FactoryFinderResolver is used to get an instance of `FactoryFinder` that
is used for lookup of resource files in the classpath in the
`META-INF/services`. It is used internally by Camel to look in .jars for
Camel components. For instance to look for the `file` component Camel
-will use the `FactoryFinder` to look the the file named `file` in
+will use the `FactoryFinder` to look the file named `file` in
`META-INF/services/org/apache/camel/component`. The `CamelContext` have
methods to inject a custom `FactoryFinderResolver`.
-== Easy configuration in Spring XML
+== Easy configuration of a custom factory finder resolver in Spring XML
We have provided easy configuration in Spring XML as you just need to
declare a spring bean with your custom factory finder resolver and Camel
