Thanks for the response Mark,
In the end the problem seems to be how the home directories on this
server are mapped.
I created a subdirectory, moved the jar and properties file inside
there. Ran it again and it worked.
I'm guessing the property file "existed" enough that the check for it
p
Based on what you've said, this is a Spring Boot related (ish) issue only
because it is loading the properties. I suggest doing this the Spring Boot
way and letting the Spring Boot/Apache Camel integration just work. If
you've not see how Spring Boot resolves properties -
https://docs.spring.io/spr
I apologize if this is either a) obvious or b) un-diagnosable because
it's my local setup.
I am working on converting an OSGI camel route to work in a deployable jar.
I am using spring-boot and decided to also switch to use java config.
My configuration class basically looks like.
@PropertySo
