You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by da...@apache.org on 2022/08/03 10:00:26 UTC

[camel] 02/02: CAMEL-18339: Java DSL (joor) - Allow compiled classes to be loadable from anywhere in Camel

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

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

commit 87fc5e2eeffbe2b91d7e355b48f5d58fb9ca45d8
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Wed Aug 3 11:39:19 2022 +0200

    CAMEL-18339: Java DSL (joor) - Allow compiled classes to be loadable from anywhere in Camel
---
 .../ROOT/pages/camel-3x-upgrade-guide-3_19.adoc    |  4 +++
 .../modules/ROOT/pages/camel-jbang.adoc            | 32 ----------------------
 2 files changed, 4 insertions(+), 32 deletions(-)

diff --git a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_19.adoc b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_19.adoc
index 35543c2a795..ed5cc083f3a 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_19.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-3x-upgrade-guide-3_19.adoc
@@ -5,3 +5,7 @@ from Camel 3.x to 3.y. For example if you are upgrading Camel 3.0 to 3.2, then y
 from both 3.0 to 3.1 and 3.1 to 3.2.
 
 == Upgrading Camel 3.18 to 3.19
+
+=== camel-api
+
+Added `addClassLoader` method to `org.apache.camel.spi.ClassResolver`.
diff --git a/docs/user-manual/modules/ROOT/pages/camel-jbang.adoc b/docs/user-manual/modules/ROOT/pages/camel-jbang.adoc
index 207a4c72d32..08cb83cb8be 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-jbang.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-jbang.adoc
@@ -545,38 +545,6 @@ There is basic support for including regular Java source files together with Cam
 and let Camel JBang runtime compile the Java source. This means you can include smaller utility
 classes, POJOs, Camel Processors and whatnot that the application needs.
 
-If any of these beans must be used/shared in the Camel application then they must be shared via bean ids,
-and not via classloading.
-
-Given a bean as below:
-
-[source,java]
-----
-@org.apache.camel.BindToRegistry("helloBean")
-public class HelloBean {
-
-    public String greeting() {
-        return "Hello World";
-    }
-}
-----
-
-Notice how the class is annotated with `@BindToRegistry`, to assign the bean an id, which
-we can use to call the bean from Camel routes such as:
-
-TIP: Instead of using `@BindToRegistry` you can also use Spring or Quarkus annotations (see further below).
-
-[source,yaml]
-----
-- from:
-    uri: "timer:yaml"
-    parameters:
-      period: "1000"
-    steps:
-      - bean: "helloBean"
-      - log: "${body}"
-----
-
 IMPORTANT: The Java source files cannot use package names. This may change in the future.
 
 === Dependency Injection in Java classes