Spring Mock Test 9

1. More complicated return codes can be returned by creating and declaring a top-level bean that implements the interface:-

2. To determine the next step is the simplest example of a conditional flow.

3. You want to control how steps are executed, perhaps to eliminate a needless waste of time by:-

4. Transaction capabilities are built on top of the first class support already provided by the core Spring framework.

5. To parameterize a job, which is then available to your steps through Spring Batch expression language.

6. If you want to vary the execution flow based on some logic more complex than a job’s ExitStatuses:-

7. Class which delegates the task of delimiting fields and records within a file to a LineMapper, which in turn delegates the task of identifying the fields within that record, to LineTokenizer.

8. Spring Batch provides a mechanism to offload processing to another process.

9. no-rollback-exception-classes element Exception classes that should not cause the transaction to roll back.

<step id = "step2">
   <tasklet>
           <chunk reader="reader" writer="writer" commit-interval="10" />
           <no-rollback-exception-classes>
           <include class="com.yourdomain.exceptions.YourBusinessException"/>
           </no-rollback-exception-classes>
   </tasklet>
</step>

10. The most fundamental support for gateways comes from the Spring Integration class:-