Also you may want to reach out the wildfly-camel team to get help from them. It seems there is some room for improvement / little bug in there. It should IMHO be possible to specify a different quartz.properties file for the quartz component to use. It surely is possible with vanilla Apache Camel.
https://github.com/wildfly-extras/wildfly-camel On Thu, Nov 10, 2016 at 12:27 PM, freakwave10 <[email protected]> wrote: > Sure: > > Wildfly 10.1 > Apache Camel Subsystem: 4.3.0 > > I have no routes defined in the standalone-full.xml of wildfly, so the only > entry is: > > <subsystem xmlns="urn:jboss:domain:camel:1.0"/> > > My application is deployed in an ear file using CDI/deltaspike/Quartz2/ .... > > So I have a quartz scheduler up and running. > At the end I want to define my own scheduler configuration just for camel. > But here I was completely unsuccessful of telling the camel-quartz component > to use a different quartz.properties. > > Thanks for your help, > > Wolfgang > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/quartz2-component-on-wildfly-10-1-tp5789975p5789999.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
