From 8dc6bc10913c505f799c69ffce8cb9faa375e78f Mon Sep 17 00:00:00 2001 From: dsyer Date: Wed, 29 Apr 2009 14:36:32 +0000 Subject: [PATCH] BATCH-1215: rename class --- src/site/docbook/reference/readersAndWriters.xml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/site/docbook/reference/readersAndWriters.xml b/src/site/docbook/reference/readersAndWriters.xml index b2ec8c8e2..28b6252c5 100644 --- a/src/site/docbook/reference/readersAndWriters.xml +++ b/src/site/docbook/reference/readersAndWriters.xml @@ -2200,13 +2200,13 @@ database has its own strategy for providing paging support, we need to use a different PagingQueryProvider for each supported database type. There is also the - SimpleDelegatingPagingQueryProvider that will + SqlPagingQueryProviderFactoryBean that will auto-detect the database that is being used and determine the appropriate PagingQueryProvider implementation. This simplifies the configuration and is the recommended best practice. - The SimpleDelegatingPagingQueryProvider + The SqlPagingQueryProviderFactoryBean requires that you specify a select clause and a from clause. You can also provide an optional where clause. These clauses will be used to build an SQL statement combined with the required sortKey. @@ -2223,7 +2223,7 @@ class="org.springframework.batch.item.database.JdbcPagingItemReader"> <property name="dataSource" ref="dataSource"/> <property name="queryProvider"> - <bean class="org.springframework.batch.item.database.support.SimpleDelegatingPagingQueryProvider"> + <bean class="org.springframework.batch.item.database.support.SqlPagingQueryProviderFactoryBean"> <property name="selectClause" value="select id, name, credit"/> <property name="fromClause" value="from customer"/> <property name="whereClause" value="where status=:status"/>