Hello.
Thanks for your answer. I'm a bit disappointed : I can prototype as
simple blueprints, without packaging, almost all my Camel routes, except
the sql component. Could you please explain why the sql URI including
the "classpath" is not interpreted the same way when running from a jar
bun
Hi
That is not possible. You cannot drop a .sql file into the deploy
folder of karaf, and assume it knows how to deploy that.
You need to put the sql script somewhere in the file system, and use
file: to refer to the file.
Or bundle it together with your camel app. Or bundle it in another
.jar (m
Hello.
I've already used the sql component using the a "classpath" external
script in blueprint.
For example :
Now I'm trying the same, but instead of a packaged jar bundle, I'd
like to test from a xml blueprint directly put in the deploy folder of
my servicemix.
The "classpath" keywork see
