search

zanetm / myschedule

Automatically exported from code.google.com/p/myschedule
0 stars 0 forks source link

Make the GroovyScriptJob more generic #2

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Instead of hardcoded with groovy quartz job, we should make it generic engough 
to use JDK's ScriptEngine interface. This way user may switch to different 
engine by simply set a property in the job data map. Use JRuby instead of 
Groovy for example.

JDK comes with a default Rhino (JavaScript) script engine already, so this 
should be very portable and flexible.

Original issue reported on code.google.com by saltnlight5 on 9 Sep 2011 at 2:34

GoogleCodeExporter commented 9 years ago 
We should resolve Issue10 before looking into this one.

Original comment by saltnlight5 on 4 Oct 2011 at 1:59

GoogleCodeExporter commented 9 years ago 
Done in d12ec2033709. Renamed the class from GroovyScriptingJob to 
ScriptingJob, and it has been moved into quartz-extra sub module.

Original comment by saltnlight5 on 5 Oct 2011 at 4:10

GoogleCodeExporter commented 9 years ago

Original comment by saltnlight5 on 18 Oct 2011 at 2:04