davsclaus commented on issue #1422:
URL: https://github.com/apache/camel-k/issues/1422#issuecomment-618252275
Okay fixed/improved this for Camel 3.3, which camel-k will pickup later.
This is an automated message from the
davsclaus commented on issue #1422:
URL: https://github.com/apache/camel-k/issues/1422#issuecomment-618246148
Created a ticket
https://issues.apache.org/jira/browse/CAMEL-14955
This is an automated message from the Apache
davsclaus commented on issue #1422:
URL: https://github.com/apache/camel-k/issues/1422#issuecomment-618242115
Okay I am working on doing 2 passes where we first do primitive / simple
types so we can do the String field injection first, before doing the bean
davsclaus commented on issue #1422:
URL: https://github.com/apache/camel-k/issues/1422#issuecomment-617974332
Yeah surely as that was how BindToRegistry was intended/designed to be liked
a spring @Bean that creates an output that are stored in the registry. And as
input you have the
davsclaus commented on issue #1422:
URL: https://github.com/apache/camel-k/issues/1422#issuecomment-617969460
Ah yeah @lburgazzoli its an ordering, bind to registry is taking precedence.
But you could argue that field injections should come before?
Its all in this class
davsclaus commented on issue #1422:
URL: https://github.com/apache/camel-k/issues/1422#issuecomment-617952519
Ah yeah both examples should ideally work, the latter requires Camel 3.2.
But for the 1st we need to ensure that camel-k creates an instance of the
`MyBuilder` via Camel's
