Jakarta Batch CDI integration language over-specifies behavior and wrongly describes implementation(Weld)-specific behavior

[scottkurz]

See discussion: https://github.com/eclipse-ee4j/batch-tck/pull/69

This paragraph in particular needs rework, and maybe the enclosing section? https://jakarta.ee/specifications/batch/2.1/jakarta-batch-spec-2.1#consequences-and-suggested-patterns

[rzo1]

In this context, it might also be required to re-write

"The @BatchProperty annotation identifies an injection as a batch property. A batch property has a name (name) and, in case of a field injection, also has a default value. @BatchProperty is used to assign batch artifact property values from Job XML to the batch artifact itself. Note that @BatchProperty is used with the standard @Inject annotation (jakarta.inject.Inject) ..." [1]

This clearly states it: no BatchProperty without @Inject

and

A batch runtime must support injection of the CDI Bean representing the batch property via method parameter and constructor parameter injection, in addition to supporting field injection. [2]

Given these paragraphs, the valid options are:

• param injection
• ct injection
• field injection but no CDI.current().select()