You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2019/12/08 09:01:24 UTC

[GitHub] [camel-quarkus] lburgazzoli opened a new issue #526: Re-introduce RoutesBuilderBuildItem

lburgazzoli opened a new issue #526: Re-introduce RoutesBuilderBuildItem
URL: https://github.com/apache/camel-quarkus/issues/526
 
 
   RoutesBuilderBuildItem were used to set routes builder to camel-main at build time and then we changed it to put those discovered routes to the camel registry.
   
   It appear that it was a wrong decision as routes from the registry are not subject to Camel's DI which seems be correct as those routes are coming from i.e. a container such as ArC thus they should rely on container's DI. 
   
   Of course mixed DI i.e. CDI + CamelDI won't work.
   
   @davsclaus what should be the right way of doing this ? One option could be that we do always apply Camel's DI to any route and let the container do it's own job.
   
   As workaround I've implemented https://github.com/apache/camel-quarkus/pull/525

----------------------------------------------------------------
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


With regards,
Apache Git Services