You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the namespace is used to define a step within a job definition, the parser does not store the step's "name" attribute on the step. Instead, the name stored in the step execution is a generated name, for example "(inner bean)#3".
Dan Garrette opened BATCH-1004 and commented
When the namespace is used to define a step within a job definition, the parser does not store the step's "name" attribute on the step. Instead, the name stored in the step execution is a generated name, for example "(inner bean)#3".
<job id="skipJob">
<step name="step1">
<tasklet ... />
StepExecution: id=0, name=(inner bean)#3, ...
Affects: 2.0.0.M3
Referenced from: commits 822f8bb, 459f7d5, 2898861, e68d9a2
The text was updated successfully, but these errors were encountered: