Terracotta Discussion Forums

Hello,

I'm trying to migrate my application from Quartz 1.8 to 2.1. Our scheduler fired both persisted and non-persisted jobs and triggers.

So, we used 'volatility' property on jobs and triggers. It seems this notion has disapeared from Quartz 2.1. Is there any way to handle both persisted and not persisted tirggers with a scheduler ?

Thanks

Hello,
this question has already been answered in our forum , see :
http://forums.terracotta.org/forums/posts/list/6960.page

Thanks for the response.

Nevertheless, @DisallowConcurrentExecution and @PersistJobDataAfterExecution mentioned in the post doesn't covered my use case.

I understand that volatility capabilities have been removed from Quartz 2. It was very usefull for us to can mix persisted and non-persisted jobs without have to instantiate two different schedulers.

So, I will re-design my scheduler to remove manually at each startup the non persisted triggers.