ppalaga commented on issue #617: Build time Camel service resolution URL: https://github.com/apache/camel-quarkus/issues/617#issuecomment-574650783 > After brainstorming a little bit more with @davsclaus we probably need to revisit how we load such services and we probably need a smart FactoryFinders which takes over the role of the registry for most of the discovery so we can keep the usual camel behaviour where registry is used to provide alternative implementations for what the it is defined by service factories. Sounds good. > We probably can have some build items that control how the discovered services are handled i.e.: > > 1. a build item can control that some services need to be instantiated and they should probably a good candidates to be stored into the registry (i.e. components) Yes, that's what we do for all (except filter-blacklisted) services ATM. > 2. a build item can control what services need to be discovered Could you please define "need to be discovered"? Is it somehow to imply, that we are going to make some services non-discoverable at runtime (e.g. by not including the service file in the app)? > 3. a build item can control what service files have to be backed into the final native image > 4. a build item can control what service files have to be "pre-loaded" in the form of a class What possible reasons are there for having both 3. and 4.? They seem to be serving the same purpose, don't they? Having just one of them would make our code simpler.
---------------------------------------------------------------- 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 With regards, Apache Git Services
