Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
CronTriggerBean extends CronTrigger - this causes an IncompatibleClassChangeError with quartz 2.0.2 on the classpath, because CronTrigger is an interface in quartz 2.
Quartz 2 being around for a couple of months now, it will be good to upgrade spring to support it.
Note that this issue is not manifested in Tomcat 6 - only in Tomcat 7 (but it is missing in the version drop-down). I believe this is a classloader change, so I'm also reporting an issue to Tomcat. (We are not using this particular class, but tomcat still loads it).
Affects: 3.1 M2
Juergen Hoeller commented
I'm closing this as "Won't Fix" from the perspective of CronTriggerBean since we have no intention to ever upgrade that class to Quartz 2.0. Note that the rest of Spring's Quartz support is Quartz 2.0 compatible now, as of Spring 3.1 RC1 (see #13006). We're just keeping CronTriggerBean and co for our ongoing compatibility with Quartz 1.x.
Tomcat really shouldn't be loading classes that the application isn't using. We're relying on that in quite a few places. So if you're not actually using CronTriggerBean, I'd definitely consider this a problem in Tomcat.
Bozhidar Bozhanov commented
Agreed. In fact the issue went away and I can't reproduce it anymore, so it's not even Tomcat's problem, but perhaps some weird combination of tomcat + eclipse WTP + java7 "mishap". Sorry for hastily reporting it here.
Martin Vanek commented
I have had the similar issue, but after installing Tomcat 7.0.25 this annoying issue vanished.
I guess that this issue is also related to #13585 and more https://issues.apache.org/bugzilla/show_bug.cgi?id=52326.