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/13 17:15:48 UTC

[GitHub] [camel-k] nicolaferraro commented on issue #1135: Basic module structure for Camel K projects

nicolaferraro commented on issue #1135: Basic module structure for Camel K projects
URL: https://github.com/apache/camel-k/issues/1135#issuecomment-565526279
 
 
   You can run multiple files in a Camel K integration, it works also if they are written in different languages. Just run:
   
   ```
   kamel run --name thename Routes1.java Routes2.java others.xml
   ```
   
   It runs as a single integration named `thename`.
   
   The "single file model" is the default model we're pushing for, but if it makes sense, I think there are no problems in collapsing multiple integration files into a single integration (often it makes sense for a performance point of view, to save some CPU/memory since it uses a single JVM).
   
   I feel that generic supporting methods and classes are better placed in an external "jar", so that one separates the glue (routes) from the business logic.
   

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