You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "jamesnetherton (via GitHub)" <gi...@apache.org> on 2023/08/17 14:02:13 UTC

[GitHub] [camel-quarkus] jamesnetherton commented on pull request #5020: Add codestart for camel-quarkus-kotlin

jamesnetherton commented on PR #5020:
URL: https://github.com/apache/camel-quarkus/pull/5020#issuecomment-1682344935

   Thanks all for the feedback! I forgot I even opened this PR :stuck_out_tongue:
   
   > It looks like assertion that content is well generated. Does it also check that the generated code is runnable ?
   
   The test framework can run the tests in the generated project.
   
   > There is also the question of how well codestart behaves when mixing multiple extensions
   
   Yes, composability is a tricky problem. It needs more thought, but you can have quite complex logic in the codestart templates to help with that.
   
   >  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) ?
   
   I don't think creating routes for specialized components is ever going to be achievable for a codestart. There could be multiple endpoint URI options required, CDI beans needed, configuration properties etc. I saw the initial goal as being able to bootstrap a simple app with a basic `RouteBuilder`, together with a test. It's for the user to deal with the specifics of their app.


-- 
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-unsubscribe@camel.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org