Hi,

we have configured two jobs with the same tasklet in the first step:

First Job:

<batch:job id="job1" parent="baseJob">
<batch:step id="stepRfhRemover">
<batch:tasklet>
<bean class="eu.unicredit.zmx.batch.tasklet.RfhRemoverTa sklet" scope="step">
<property name="inFile" value="A"/>
<property name="outFile" value="B"/>
</bean>
</batch:tasklet>
</batch:step>
</batch:job>

Second Job:

<batch:job id="job2" parent="baseJob">
<batch:step id="stepRfhRemover">
<batch:tasklet>
<bean class="eu.unicredit.zmx.batch.tasklet.RfhRemoverTa sklet" scope="step">
<property name="inFile" value="C"/>
<property name="outFile" value="D"/>
</bean>
</batch:tasklet>
</batch:step>
</batch:job>

If we execute job2 we see that the tasklet is injected with the values from job1 (A and B). We found out, that if we choose different names for the steps (for example id="job1.stepRfhRemover" and id="job2.stepRfhRemover"), everything works fine.

In our opinion a step should be unique for a job even it has the same id. Is this a bug or feature?

Bye
Achim