[GitHub] [camel-k] davesargrad edited a comment on issue #1135: Basic module structure for Camel K projects

[GitBox <gi...@apache.org>]

davesargrad edited a comment on issue #1135: Basic module structure for Camel K projects
URL: https://github.com/apache/camel-k/issues/1135#issuecomment-565500808
 
 
   @nicolaferraro I was about to ask this. So is it true that I currently cant create a route that uses several java classes defined in several files? Is this a major limitation, or can I simply place all those class definitions into a single ".java" file?
   
   I would think that many meaningful routes may have a handful of classes, and modularity suggests that these should go in separate files. 
   
   An example of an atomikos springboot application, that i am working to find a kamel equivalent of is found [here](https://github.com/atomikos/spring-boot-sample-jta-atomikos-logcloud/tree/master/src/main/java/sample/atomikos)
   
   If you look particularly at the [AccountService](https://github.com/atomikos/spring-boot-sample-jta-atomikos-logcloud/blob/master/src/main/java/sample/atomikos/AccountService.java), one can imagine that as a kamel enabled route that implements a kamel-enabled interface both to a jdbc endpoint, and to a jms endpoint.
   
   The application is clean, and you'd hope that a kamel variant still preserves the essence of the class structure.

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