grgrzybek opened a new pull request, #10000: URL: https://github.com/apache/camel/pull/10000
# Description This is first attempt at https://issues.apache.org/jira/browse/CAMEL-18189. `<beans>` element treated simply as root element of _Camel application_ is easy. The `<bean>` element in the Spring sense is hard, because Camel already uses `<bean>` element as bean processor. However, CAMEL-18189 is about * root element to collect routes, rests, templates, ... * add some (to be enhanced later) sort of bean registry population So I've taken existing `DIRegistry` implementation of `org.apache.camel.support.SupplierRegistry` and populated it by scanning (`org.apache.camel.spi.PackageScanClassResolver`) selected packages. Here's an example of working XML snippet: ```xml <camel-app> <component-scan base-package="org.apache.camel.dsl.xml.io.beans" /> <route id="r2"> <from uri="direct:x2"/> <bean ref="bean-from-registry" /> <to uri="mock:y2"/> </route> </camel-app> ``` where `bean-from-registry` is: ```java @Named("bean-from-registry") public class Greeter implements Processor { private final GreeterMessage message; @Inject public Greeter(GreeterMessage message) { this.message = message; } @Override public void process(Exchange exchange) throws Exception { String msg = exchange.getIn().getBody(String.class); exchange.getIn().setBody(message.getMsg() + " " + StringHelper.after(msg, "I'm ")); } } ``` And injected `GreeterMessage` is: ```java @Named public class GreeterMessage { private final String msg = "Hello"; public String getMsg() { return msg; } } ``` # Target - [+] I checked that the commit is targeting the correct branch (note that Camel 3 uses `camel-3.x`, whereas Camel 4 uses the `main` branch) # Tracking - [+] If this is a large change, bug fix, or code improvement, I checked there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change (usually before you start working on it). <!-- # *Note*: trivial changes like, typos, minor documentation fixes and other small items do not require a JIRA issue. In this case your pull request should address just this issue, without pulling in other changes. --> # Apache Camel coding standards and style - [+] I checked that each commit in the pull request has a meaningful subject line and body. <!-- If you're unsure, you can format the pull request title like `[CAMEL-XXX] Fixes bug in camel-file component`, where you replace `CAMEL-XXX` with the appropriate JIRA issue. --> - [+] I formatted the code using `mvn -Pformat,fastinstall install && mvn -Psourcecheck` <!-- You can run the aforementioned command in your module so that the build auto-formats your code and the source check verifies that is complies with our coding style. This will also be verified as part of the checks and your PR may be rejected if the checkstyle does not pass. You can learn more about the contribution guidelines at https://github.com/apache/camel/blob/main/CONTRIBUTING.md --> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
