lburgazzoli opened a new issue #1112:
URL: https://github.com/apache/camel-quarkus/issues/1112
The current factory finder set-up does not take into account additional
service defined from the factory file using prefixes, as example, the factory
file content of the file component defines two services:
class=org.apache.camel.component.file.FileComponent
strategy.factory.class=org.apache.camel.component.file.strategy.FileProcessStrategyFactory
but the current implementation puts an instance if the FileComponent class
into the registry and blindly ignore strategy.factory.class, in addition, the
current selector can't distinguish between REGISTER and DISCOVERY at service
factory property level.
We should allow to define on which key the filter is applied i.e:
* register the service identified by the property `class` in the service
factory file (note that `class` is the default and can be omitted)
```java
new CamelServicePatternBuildItem(
CamelServiceDestination.REGISTRY,
true,
"META-INF/services/org/apache/camel/component/file@class"))
```
* make the service identified by the property `strategy.factory.class`
discoverable through the factory finder (note that `class` is the default and
is automatically added if not present)
```java
new CamelServicePatternBuildItem(
CamelServiceDestination.DISCOVERY,
true,
"META-INF/services/org/apache/camel/file@strategy.factory.class");
```
The same syntax can be used in the configuration files
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
