[BATCHEE-140] Propagate JobOperatorImpl instance to SimpleJobExecutionCallbackService properly

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.5-incubating
• Fix Version/s: 0.6
• Component/s: jbatch-core
• Assignee: Unassigned
• Reporter: Christian Berger
• Created: 19/Apr/20 19:51
• Updated: 20/Apr/20 05:36
• Resolved: 20/Apr/20 05:36

Description

While testing my code I've figured out that passing an individual JobOperatorImpl instance is not working as expected when using this code snippet:

final JobOperator operator = new JobOperatorImpl(new ServicesManager() {{
            init(new Properties() {{
                setProperty(PersistenceManagerService.class.getSimpleName(), MemoryPersistenceManagerService.class.getName());
            }});
        }});

I'm going to implement a fix as suggested by rmannibucau :

@chberger
 yes, 
org.apache.batchee.container.services.callback.SimpleJobExecutionCallbackService#checkIsDone
 must change to use the right joboperator if the joboperator is a 
JobOperatorImpl. Guess it is just a matter of propagating it at 
org.apache.batchee.util.Batches#waitFor(javax.batch.operations.JobOperator,
 long)

Issue Links

• links to: GitHub Pull Request #3