weimeilin79 opened a new issue #1821: URL: https://github.com/apache/camel-k/issues/1821
Currently POJO is no longer taken in by Camel K. Instead of restricting and directly rejecting it, can we have a window open for this scenario, provide it as an optional feature. Without the support for POJO meaning there is no easy DEV mode for Camel K, basically it’s the death of live coding. Instead of seeing the beauty of seeing code directly running on K8s, now the flow goes like this: Developer creates another project for ANY bean/helper/util class, compiles, and uploads to jitpack, (what if it’s enterprise env? Developers go through another process of uploading it? Meaning the OPS needs to get either Nexus or Jitpack whatever ready? ) Or just do an awful long javascript like all-in-one java class? Where is the agility? Where is the fast time to deploy? Yes, separating it could be better for unit testing, (I understand the need for unit testing? But aren’t we pushing BDD for integration code? ) BUT!!! how about the painful process before unit test, during development? It’s not like you can run Camel K route easily locally to test the utility? Meaning the developer has to shift between local and k8s .. It'll just be easier to do a simple Quarkus java app, at least there is no two separate env I need to work with, and two separate deployments process. I know there would be problems for Quarkus runtime, and native compile and maybe longer build time. But having to do things separately not only breaks the train of thoughts, but also requires developers to do a lot of extra work. And another thing is about the positioning with Kamelet, if Camel K used JUST for route? I don’t see a clear definite line between Kamelet and this? Can we have an option for POJO, say if this is there, then default runtime won't be Quarkus or with Native build. And warning on slower build time.. etc.. ---------------------------------------------------------------- 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: [email protected]
