Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spring should support Quartz 2.0 CronTrigger interface [SPR-8581] #13225

Closed
spring-issuemaster opened this issue Aug 2, 2011 · 3 comments

Comments

@spring-issuemaster
Copy link
Collaborator

@spring-issuemaster spring-issuemaster commented Aug 2, 2011

Bozhidar Bozhanov opened SPR-8581 and commented

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

Issue Links:

  • #13081 java.lang.IncompatibleClassChangeError --> with new Version Of Quartz (2.0.0) !!!
  • #13006 Need support for Quartz 2.0
@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

@spring-issuemaster spring-issuemaster commented Aug 2, 2011

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.

Juergen

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

@spring-issuemaster spring-issuemaster commented Aug 2, 2011

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.

@spring-issuemaster

This comment has been minimized.

Copy link
Collaborator Author

@spring-issuemaster spring-issuemaster commented Feb 21, 2012

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.