Can you suggest some (quick) ways to debug this?
2017-10-04 08:42:41.704 main JobOperatorTest - INFO Getting operator
Exception in thread "main" java.util.ServiceConfigurationError: javax.batch.operations.JobOperator: Provider org.jberet.operations.JobOperatorImpl could not be instantiated
at java.util.ServiceLoader.fail(ServiceLoader.java:232)
at java.util.ServiceLoader.access$100(ServiceLoader.java:185)
at java.util.ServiceLoader$LazyIterator.nextService(ServiceLoader.java:384)
at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:404)
at java.util.ServiceLoader$1.next(ServiceLoader.java:480)
at javax.batch.runtime.BatchRuntime.getJobOperator(BatchRuntime.java:57)
at com.awginc.batch.JobOperatorTest.process(JobOperatorTest.java:27)
at com.awginc.batch.JobOperatorTest.main(JobOperatorTest.java:41)
Caused by: org.jboss.weld.exceptions.DeploymentException: WELD-001414: Bean name is ambiguous. Name csvItemReader resolves to beans:
- Managed Bean [class org.jberet.support.io.CsvItemReader] with qualifiers [@Default @Any @Named],
- Managed Bean [class org.jberet.support.io.CsvItemReader] with qualifiers [@Default @Any @Named]
at org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:134)
at org.jboss.weld.bootstrap.ConcurrentValidator$5.doWork(ConcurrentValidator.java:130)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:63)
at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:56)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
are there 2 jberet-support.jar files in the runtime classpath?
Looks like Weld found 2 copies of the same class org.jberet.support.io.CsvItemReader. Maybe 2 different versions of jberet-support.jar are packaged in by accident?