views:

33

answers:

1

Is it possible to configure (registering with scheduler) non-global job listeners declaratively in properties file (rather than programmatically) similar to configuring global listeners?

Check here for:

  1. Programmatically adding a global job listener
  2. Programmatically adding a non-global job listener

EDIT: Example for configuring a Global JobListener:

org.quartz.jobListener.NAME.class = com.foo.MyListenerClass
org.quartz.jobListener.NAME.propName = propValue
org.quartz.jobListener.NAME.prop2Name = prop2Value
A: 

Meantime, I'm also reading that Non-global listeners (and having a job/trigger name its listeners) are considered deprecated and would be completely removed in Quartz v2.0.

Check here on this for further reading.

But still I'm looking/finding out whether this can be configured/registered declaratively in atleast Quartz v1.8.3, which is the version I'm currently using.

Gnanam