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/05 10:00:14 UTC

[GitHub] [camel-quarkus] ppalaga commented on issue #511: Pre-configure reoute builders at build time

ppalaga commented on issue #511: Pre-configure reoute builders at build time
URL: https://github.com/apache/camel-quarkus/issues/511#issuecomment-562057669
 
 
   Related https://github.com/apache/camel-quarkus/issues/97 and partly also https://github.com/apache/camel-quarkus/issues/253 
   
   Yes, this might help to solve the problem, although hard to say how reliably we can pre-configure a route in this way without knowing its complete model at build time. 
   I am asking myself, whether we would still need this kind of annotation if we had the complete Route model (which we do not ATM due to how RoutesBuilder is designed) at build time. We could perhaps figure out many of the necessary parts, but probably not all: e.g. a Route definition can contain an ad hoc lambda, that would be impossible to introspect at build time. So we'd perhaps still need some way (an annotation or an app.props entry) to pass the info to the Processor.
   

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