[Building Sakai] a quartz question
Bryan Holladay
holladay at longsight.com
Wed Jan 9 12:12:50 PST 2013
This is what happens when you have two exact classes that are compiled in
two different locations. I've ran into this several times, here's one
example:
https://jira.sakaiproject.org/browse/SAK-19896
Essentially, you need to find where both are being compiled (jar'ed) and
only depend on 1 of them
On Wed, Jan 9, 2013 at 3:07 PM, Zhen Qian <zqian at umich.edu> wrote:
> Hello, Sakai Developers:
>
> We have had some local quartz job stopped working since 2.9 upgrade.
>
> The code uses "StdSchedulerFactory.getDefaultScheduler();" to get the
> Scheduler instance.
>
> However, it now throws the following exception:
>
> "org.quartz.SchedulerConfigException: Unable to instantiate class load
> helper class: org.quartz.simpl.CascadingClassLoadHelper cannot 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]"
>
> We are with quartz 1.5.2.
>
> Any suggestions/ideas to avoid this problem?
>
> Thanks,
>
> - Zhen
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130109/c24ba07f/attachment.html
More information about the sakai-dev
mailing list