From f39deb298bda2a95324549267b2affd5b8db1f9d Mon Sep 17 00:00:00 2001 From: dsyer Date: Tue, 5 May 2009 11:30:53 +0000 Subject: [PATCH] BATCH-1234: Change FINISED To COMPLETED --- src/site/docbook/reference/step.xml | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/src/site/docbook/reference/step.xml b/src/site/docbook/reference/step.xml index 39c82197a..d8b9f2e9a 100644 --- a/src/site/docbook/reference/step.xml +++ b/src/site/docbook/reference/step.xml @@ -1035,13 +1035,15 @@ ItemWriter. Spring Batch provides the TaskletStep for this scenario. - The Tasklet is a simple interface that has - one method, execute, which will be a called - repeatedly by the TaskletStep until it either - returns FINISHED or throws an exception to signal a - failure. Each call to the Tasklet is wrapped in a - transaction. Tasklet implementors might call a - stored procedure, a script, or a simple SQL update statement. To create a + The Tasklet is a simple interface + that has one method, execute, which will + be a called repeatedly by the TaskletStep + until it either returns RepeatStatus.FINISHED + or throws an exception to signal a failure. Each call to + the Tasklet is wrapped in a + transaction. Tasklet implementors might + call a stored procedure, a script, or a simple SQL update + statement. To create a TaskletStep, the 'ref' attribute of the <tasket/> element should reference a bean defining a Tasklet object; no <chunk/> element should be @@ -1113,7 +1115,7 @@ files[i].getPath()); } } - return RepeatStatus.FINISHED; + return RepeatStatus.COMPLETED; } public void setDirectoryResource(Resource directory) {