[GitHub] [camel-k] lburgazzoli edited a comment on issue #1870: camel.component.* properties not being respected under Quarkus runtime

[GitBox <gi...@apache.org>]

lburgazzoli edited a comment on issue #1870:
URL: https://github.com/apache/camel-k/issues/1870#issuecomment-758091720


   The issue is related to the auto wired capabilities of camel-main that by default, auto configures components so in this case if there is an instance of a cache manager or a kafka client, then such instance is bound to the related components and other options may not have effect (depending on how the component is implemented but usually pre-configured instances have higher priority). 
   
   When running on quarkus, the advantage of auto wiring is that the client/manager/etc may be optimized for quarkus and some of the set-up can be done at build time which may determine a faster startup and improved footprint.
   
   As a workaround, you can disable automatic binding with the following property:
   
       camel.main.autowired-enabled = false
   
   At this point camel-main does not attempt any more to auto wire beans, thus the properties are then taken into account.
   
   @davsclaus wonder if we should have an option to disable auto-wiring on a per component basis


----------------------------------------------------------------
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:
users@infra.apache.org