According JBeret specification JBeret should be able to @Inject @BatchProperty File file, but it works only in special curcumstance. about jsr352

[chengfang]

Batch jobs are defined in xml format and thus all batch job configurations are expressed in string-based values. I think this is a pretty fundamental part of the batch spec (JSR 352), though I have to admit this does impose some restrictions on batch applications, for instance, there is no typed non-string objects for configuration.

From a technical point of view, java.util.Properties are used in various parts of the spec to hold job parameters, partition properties, etc. This also implies string-based keys and values are expected. Since java.util.Properties is a subclass of java.util.Hashtable, so you can still call its put method to add non-string values, but this value may very likely be ignored.

[chengfang]

To inject object types into batch artifacts with more flexibility, you may want to consider using CDI. WE use CDI injections in some of the batch artifacts in jberet-support modules, for instance,

https://github.com/jberet/jberet-support/blob/master/src/main/java/org/jberet/support/io/JmsItemReaderWriterBase.java#L41