Hi, Another thing to look at, are you using a common quartz instance that has job persistence enabled (e.g. a database job store instead of RAMJobStore)?
John On Thu, Nov 10, 2016 at 7:10 AM Claus Ibsen <[email protected]> wrote: > Hi > > You can maybe use CDI @Produces bean that has a method that produces > the component > > @Produces > public QuartzComponent myQuartzComponent(CamelContext camelContext) { > // code here to setup the component > } > > That is more normal way of doing stuff like that with CDI. > > However can you show us a bit more where you create that quartz > component and add to CamelContext? Do you do that from a RouteBuilder > in the configure method or where? > > We had a recent issue with OSGi blueprint where some users did that > and the component resolver couldnt find the component. Maybe similar > fix is needed for wildfly-camel / camel-cdi etc. > > https://issues.apache.org/jira/browse/CAMEL-10394 > > 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 >
