Uploaded image for project: 'JBeret'
  1. JBeret
  2. JBERET-551 Support injection of JobOperator
  3. JBERET-552

Inject JobOperator to batch artifacts defined with batch.xml or FQCN

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Major Major
    • 2.1.0.Final
    • None
    • jberet-core
    • None

      TCK test: InjectImplProvidedJobOperatorTests#testCDIJobOperatorInject checks JobOperator can be injected into batch artifacts defined as CDI bean, or with batch.xml, or with FQCN.

      Currently the latter 2 cases are failing:

      INFO: starting job with refName = com.ibm.jbatch.tck.artifacts.cdi.JobOperatorInjectedBatchlet
      May 13, 2022 4:58:54 PM org.jberet.tools.AbstractJobXmlResolver resolveJobXml
      INFO: JBERET000030: Resolved job jar:file:/Users/cfang/.m2/repository/jakarta/batch/com.ibm.jbatch.tck/2.1.0/com.ibm.jbatch.tck-2.1.0.jar!/META-INF/batch-jobs/cdi_inject_beans.xml
      May 13, 2022 4:58:54 PM org.jberet.runtime.runner.BatchletRunner run
      WARN: JBERET000001: Failed to run batchlet org.jberet.job.model.RefArtifact@252ac06d
      java.lang.NullPointerException
          at com.ibm.jbatch.tck.artifacts.cdi.JobOperatorInjectedBatchlet.process(JobOperatorInjectedBatchlet.java:46)
          at org.jberet.runtime.runner.BatchletRunner.run(BatchletRunner.java:74) 

              cfang@redhat.com Cheng Fang
              cfang@redhat.com Cheng Fang
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: