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 99d75cc Fixed small typo
99d75cc is described below
commit 99d75cc6f00bba0fa0d0f9638496dc723f27a669
Author: aldettinger <aldettin...@gmail.com>
AuthorDate: Wed Mar 27 19:38:48 2019 +0100
Fixed small typo
---
MIGRATION.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MIGRATION.md b/MIGRATION.md
index 5786ffe..2435385 100644
--- a/MIGRATION.md
+++ b/MIGRATION.md
@@ -58,7 +58,7 @@ Migrating custom components
You should depend on `camel-support` and not `camel-core` directly.
-The classes from `org.apache.camel.impl` that was intended to support Camel
developers building custom components has been moved out of `camel-core` into
`camel-support` into the `org.apache.camel.support` package. For example
classes such as `DefaultComponent`, `DefaultEndpoint` etc has been moved and
migration is nessasary.
+The classes from `org.apache.camel.impl` that was intended to support Camel
developers building custom components has been moved out of `camel-core` into
`camel-support` into the `org.apache.camel.support` package. For example
classes such as `DefaultComponent`, `DefaultEndpoint` etc has been moved and
migration is necessary.
// TODO: Should we create a camel2-support JAR with an adapter to bridge
between 2.x and 3.0
@@ -191,7 +191,7 @@ The class
`org.apache.camel.management.JmxSystemPropertyKeys` has been moved to
#### camel-test
-If you are using camel-test and override the `createRegistry` method, for
example to register beans from the `JndiRegisty` class, then this is no longer
nessasary, and instead
+If you are using camel-test and override the `createRegistry` method, for
example to register beans from the `JndiRegisty` class, then this is no longer
necessary, and instead
you should just use the `bind` method from the `Registry` API which you can
call directly from `CamelContext`, such as:
context.getRegistry().bind("myId", myBean);
