Inconsistent transaction manager configuration between XML and Java config styles

[fmbenhassine]

trafficstars

With the XML configuration style, the transaction manager is configurable as an attribute of the tasklet element. This means other step types (partition step, flow step, etc) do not have this attribute, which makes sense since those step types do not require a transaction manager by design (see here).

With Java configuration on the other hand, the transaction manager is configurable at the StepBuilderHelper level, which is common to all step builders. While this is not an issue in itself, it requires the configuration of something that is not required in the first place, in addition to introducing an inconsistency between the two configuration styles:

The transaction manager configuration should be moved down from StepBuilderHelper to AbstractTaskletStepBuilder in order to make this consistent with XML config.