You cannot use JVM or ENV parameters, but you can configure the propertiesFile with either file: or classpath: as prefix to load it from either of those.
Its using Camel's ResourceLoader (Helper) so we could consider adding support for specifying an ENV or JVM prefix so its using that, eg propertiesFile=env:MY_PROP We do have property placeholder http://camel.apache.org/using-propertyplaceholder.html However that don't afair apply to options on component level configure spring-bean style. You would need to find a way if spring-boot / <bean> offers that. Or with spring boot you can add a bit of java code that creates the QuartzComponent with @Bean or @Produces (cant remember the annotation) and then write the java code it takes to read that JVM parameter to find the file location and configure this using java code. On Mon, Jan 23, 2017 at 11:30 AM, Deepak kumar <dksahoo...@gmail.com> wrote: > We have a spring boot backed camel project and we are using a camel-quartz2 > component . The problem is by default the quartz.properties file is expected > to be present in org.quartz directory inside the src/main/resources > directory . Is there any possible way where i can give the location of the > quartz.properties file as a jvm parameter when i start my project . > Something like -- -Dquartz= D://test//quartz.properties > Also i tried the "propertiesFile" config using spring bean , this also > didn't work for me. Any suggestions.. > > Regards, > Deepak > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/camel-quartz2-scheduler-external-quartz-properties-file-tp5793004.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
