squakez commented on issue #770: URL: https://github.com/apache/camel-k-runtime/issues/770#issuecomment-2677908551
> ` Maybe the difference relies on how the Route it's been loaded, camel k loads the route at runtime, but I'm not sure. Yep, likely this is the reason as it may have different classloaders involved, at least in java. It would be interesting to try with other DSL such as YAML as I think in that case we'd be in a similar situation in local execution of Camel Quarkus as well. IIRC, during a build of a Java route, the class is packaged as part of the dependency, which is something not happening in Camel K. -- 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
