Ok I found the problem following this link : http://camel.apache.org/how-to-use-extra-camel-componets-in-servicemix-camel.html
Regards William On Tue, Nov 30, 2010 at 4:42 PM, will mad <[email protected]> wrote: > Hi, > > I work on a service assembly including a camel service unit. > > This camel service unit has a route with a quartz timer : > from("quartz://initEquipments").to("direct:initEquipments"); > > When I deploy the service-assembly for the first time, there is no problem. > But as soon as I deploy a new version of the service assembly the following > exception is raised : > > Failed to resolve endpoint: quartz://initEquipments due to: > org.apache.camel.RuntimeCamelException: Could not auto create component: > quartz > > org.apache.camel.ResolveEndpointFailedException: Failed to resolve > endpoint: quartz://initEquipments due to: > org.apache.camel.RuntimeCamelException: Could not auto create component: > quartz > at > org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:351) > ... > Caused by: org.apache.camel.RuntimeCamelException: Could not auto create > component: quartz > at > org.apache.camel.impl.DefaultCamelContext.getComponent(DefaultCamelContext.java:189) > ... > Caused by: org.quartz.SchedulerConfigException: Unable to instantiate class > load helper class: org.quartz.simpl.CascadingClassLoadHelper can > not be cast to org.quartz.spi.ClassLoadHelper [See nested exception: > java.lang.ClassCastException: org.quartz.simpl.CascadingClassLoadHelper > cannot be cast to org.quartz.spi.ClassLoadHelper] > ... > Caused by: java.lang.ClassCastException: > org.quartz.simpl.CascadingClassLoadHelper cannot be cast to > org.quartz.spi.ClassLoadHelper > at > org.quartz.impl.StdSchedulerFactory.instantiate(StdSchedulerFactory.java:651) > ... > > The only option I have is to remove the data directory and restart > Servicemix. > > Environment > Windows XP > servicemix-3.3.1 > servicemix-camel-2009-01 > > Thanks for your help > Regards > William > >
