Java Reference
In-Depth Information
Houston | CA | 38635 |
| 1610 | Ann | Z | Benes | 2447 S. Greenwood Ave |
Las Vegas | NY | 55366 |
| 1612 | Erica | Z | Gates | 3141 Farnam Street |
Omaha | CA | 57640 |
| 1613 | Warren | M | Williams | 6670 S. Greenwood Ave |
Hollywood | FL | 37288 |
| 1614 | Harry | T | Darrow | 3273 Isabella Ave |
Houston | FL | 97261 |
| 1615 | Steve | O | Darrow | 8407 Infinite Loop Drive |
Las Vegas | WA | 90520 |
The other way to check the output of the job is to look at the results via the Spring Batch Admin
application. Figure 9-4 shows Spring Batch Admin's display of the results.
Details for Step Execution
Figure 9-4. Spring Batch Admin's display of the results for the step
The PreparedStatement notation is useful given most Java developers' familiarity with it. However,
the named parameter approach provided by Spring's JdbcTemplate is a much safer way to go and is the
preferred way to populate parameters in most Spring environments. With that in mind, you can put this
feature to use by making two small updates to the configuration:
Update the configuration to remove the ItemPreparedStatementSetter
implementation you wrote and replace it with an implementation of the
ItemSqlParameterSourceProvider interface.
1.
 
 
Search WWH ::




Custom Search