Previously, the batch job operator JobOperator can only be requested once from the batch runtime under JBeret SE. If it is requested more than once, an error will be thrown.

// first call
JobOperator jobOperator = BatchRuntime.getJobOperator();

// use jobOperator to operate a job
...

// retrieve again, error
jobOperator = BatchRuntime.getJobOperator();

Error message:

java.util.ServiceConfigurationError: javax.batch.operations.JobOperator: Provider org.jberet.operations.JobOperatorImpl could not be instantiated

This ticket aims to investigate:

• Is it still the case on the current codebase?
• Is it a bug from JBeret SE?
• Is there any case where BatchRuntime#getJobOperator() need to be called twice?