Sometimes this requirement may jump at you: “I still want to have them as several jobs, but I want no operational overhead, and need to run them in sequence via a single launch…”.
So if you were using CommandLineJobRunner to launch these jobs, it would only be natural to aggregate those calls under your own e.g. “CommandLineMultipleJobRunner” that just delegates its calls to “CommandLineJobRunner” for each job in a list..
The only caveat is the default SystemExiter which is set to JvmSystemExiter, which makes it imposible to make more than one launch using a “CommandLineJobRunner”, since “JvmSystemExiter” does:
public void exit(int status) { System.exit(status); } |
Fortunately, there is a static accessor to override this behavior:
// disabling a default "JvmSystemExiter" to be able to run several times CommandLineJobRunner.presetSystemExiter( new SystemExiter() { public void exit( int status ) {} } ); |
Now, call “CommandLineJobRunner.main( String[] args )” as many times as you’d like.
If you have a choice, think about creating a single multi step job instead, but if you don’t have a luxury, “CommandLineMultipleJobRunner” should now be not all that hard to implement.
Batch Away! :)