[Logo] Terracotta Discussion Forums
  [Search] Search   [Recent Topics] Recent Topics   [Members]  Member Listing   [Groups] Back to home page 
[Register] Register / 
[Login] Login 
[Expert]
Statefulness and Volatility in Quartz 2  XML
Forum Index -> Quartz
Author Message
awood

neo

Joined: 04/24/2012 11:18:31
Messages: 1
Offline

Hi,

I've been tasked with moving some code from Quartz 1 to Quartz 2. The migration guide has served me well, but I did run into one case it didn't cover.

The unit tests for my project make assertions about the value of isStateful() and isVolatile() of a JobDetail. The methods aren't present in Quartz 2. Additionally, I saw in the Database Schema Changes section of the migration guide that the is_volatile and is_stateful columns have been dropped.

What's the correct way to test for statefulness and volatility? Or should I just remove those assertions from my unit tests altogether?
jhouse

seraphim
[Avatar]
Joined: 11/06/2009 15:29:56
Messages: 1654
Offline


The notion of volatility was completely removed from Quartz 2.x, so that should just be removed from your tests.

The notion of statefulness was removed (well, strongly deprecated) and replaced with two independent concepts: @PersistJobDataAfterExecution and @DisallowConcurrentExecution. The JobDetail interface therefore now has the methods isPersistJobDataAfterExecution() and isConcurrentExectionDisallowed().
 
Forum Index -> Quartz
Go to:   
Powered by JForum 2.1.7 © JForum Team