RowCallbackHandler (Spring Framework API 2.1) - Spring Framework 2.1.0 API 文档英文版

Overview

Package

Class

Use

Tree

Deprecated

Index

Help

The Spring Framework

PREV CLASS NEXT CLASS

FRAMES NO FRAMES

SUMMARY: NESTED | FIELD | CONSTR | METHOD

DETAIL: FIELD | CONSTR | METHOD

org.springframework.jdbc.core
Interface RowCallbackHandler

All Known Implementing Classes:: RowCountCallbackHandler

public interface RowCallbackHandler

An interface used by JdbcTemplate for processing rows of a ResultSet on a per-row basis. Implementations of this interface perform the actual work of processing each row but don't need to worry about exception handling. SQLExceptions will be caught and handled by the calling JdbcTemplate.

In contrast to a ResultSetExtractor, a RowCallbackHandler object is typically stateful: It keeps the result state within the object, to be available for later inspection. See RowCountCallbackHandler for a usage example.

Consider using a RowMapper instead if you need to map exactly one result object per row, assembling them into a List.

Author:: Rod Johnson, Juergen Hoeller
See Also:: JdbcTemplate, RowMapper, ResultSetExtractor, RowCountCallbackHandler

Method Summary

void processRow(ResultSet rs)
Implementations must implement this method to process each row of data in the ResultSet.

Method Summary
`void`	`processRow(ResultSet rs)` Implementations must implement this method to process each row of data in the ResultSet.

Method Detail

processRow

void processRow(ResultSet rs)
                throws SQLException

Implementations must implement this method to process each row of data in the ResultSet. This method should not call next() on the ResultSet; it is only supposed to extract values of the current row.

Exactly what the implementation chooses to do is up to it: A trivial implementation might simply count rows, while another implementation might build an XML document.

Parameters:: rs - the ResultSet to process (pre-initialized for the current row)
Throws:: SQLException - if a SQLException is encountered getting column values (that is, there's no need to catch SQLException)