[camel] 02/03: CAMEL-13456: CamelContext - Move API that are not related to end users to an ExtendedCamelContext

[da...@apache.org]

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

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

commit 48b876cbdeaf09fb3a7abb8f1aa59536f52475f9
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Mon May 20 12:55:33 2019 +0200

    CAMEL-13456: CamelContext - Move API that are not related to end users to an ExtendedCamelContext
---
 MIGRATION.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/MIGRATION.md b/MIGRATION.md
index c8766a8..4ff7b5d 100644
--- a/MIGRATION.md
+++ b/MIGRATION.md
@@ -21,6 +21,7 @@ In Camel 2.x camel-core was one JAR file, which now has been splitup into many J
 - camel-caffeine-lrucache
 - camel-cloud
 - camel-core
+- camel-jaxp
 - camel-management-api
 - camel-management-impl
 - camel-support
@@ -155,6 +156,12 @@ In Camel 2.x we have deprecated `getProperties` on `CamelContext` in favour of `
     </globalOptions>
 
 
+### Extended CamelContext
+
+The APIs on `CamelContext` has been reducded a bit to focus on relevant API for Camel end users. The advanced use-cases and for SPI and component developers, then some of the APIs from `CamelContext` has been moved to `ExtendedCamelContext` which you can access via adapt:
+
+    ExtendedCamelContext ecc = context.adapt(ExtendedCamelContext.class);
+
 ### Main class
 
 The `Main` class from `camel-core`, `camel-spring` and `camel-cdi` has been modified to only support a single `CamelContext` which was really its intention, but there was some old crufy code for multiple Camels. The method `getCamelContextMap` has been removed, and there is just a `getCamelContext` method now.