aldettinger commented on PR #5020:
URL: https://github.com/apache/camel-quarkus/pull/5020#issuecomment-1682312505
>> how do we ensure that generated codestarts can run at each version
without manual testing ?
>
> There is a test called `KotlinCodestartTest` in this PR
https://github.com/apache/camel-quarkus/pull/5020/files#diff-93ae7fb045df527f7bf6084da75695a312f6665471fe730534b8286594b96211
It looks like assertion that content is well generated. Does it also check
that the generated code is runnable ?
> >There is also the question of how well codestart behaves when mixing
multiple extensions as this the main scenario when building Camel integrations.
Maybe we could integrate a single code start per DSL and that's all...
>
> That's a valid concern. IIRC, it was mentioned very early when the
CodeStarts were introduced that the composability might be an issue. OTOH, do
our extensions really require amending some file provided by some other
extension? Maybe application.properties? Otherwise each extension could provide
its own route definition file in some particular DSL. Maybe for some
extensions, it would be hard to write such without timer. But it would be easy
for others.
More than composability related technical issues that might be solved or
not, there is the subject of how much it would make sense to code start
multiple extensions together. Like code starting an app with jms + jdbc, what
route does it make sense to generate from(timer).to(jms) + from(timer.to(jdbc)
route ? from(jms).to(jdbc) ?
--
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.
To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
