orpiske commented on PR #7714: URL: https://github.com/apache/camel/pull/7714#issuecomment-1145057417
> How are the adapters discovered? Some kind of classpath discovery? If so we have the existing FactoryFinder that we use for everything in Camel ala components, languages, health checks, and other things. > > The manifest files are stored in META-INF/services/org/apache/camel/... > > I noticed that in this PR that it may not be the location for this? It reads the properties defined in the `adapter.properties` to find the adapter to load. The bulk of work was done on #7688 and now I am updating the supported components to this behavior. In terms of code, the resolution is done in the DefaultRoute when gathering the root services [1] and then the helper searches [2] both on the classpath as well as the registry to resolve the strategy and the cache. Thanks for mentioning the `FactoryFinder`. This is still a WIP and there's more to be done, including CAMEL-18152 and CAMEL-18128, which can benefit from this. Relevant links: 1. https://github.com/apache/camel/blob/main/core/camel-base-engine/src/main/java/org/apache/camel/impl/engine/DefaultRoute.java#L646-L650 2. https://github.com/apache/camel/blob/main/core/camel-support/src/main/java/org/apache/camel/support/resume/AdapterHelper.java#L42-L70 -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
