Spring/spring-batch
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

RESOLVED - issue BATCH-127: Allow job configuration to control re-entrant behavior

Browse Source 
http://opensource.atlassian.com/projects/spring/browse/BATCH-127

Tidy Javadocs.
This commit is contained in:
dsyer
2007-12-16 12:04:03 +00:00
parent c9fccc8d85
commit a48b7847e3
1 changed files with 7 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
spring-batch-execution/src/main/java/org/springframework/batch/execution/repository/SimpleJobRepository.java
View File

@@ -109,14 +109,13 @@ public class SimpleJobRepository implements JobRepository {
* </ol>
* If this method is run in a transaction (as it normally would be) with
* isolation level at {@link Isolation#REPEATABLE_READ} or better, then this
* method should block if another transaction is already executing this
* method for the same {@link JobIdentifier}. The first transaction to
* complete in this scenario should obtain a valid {@link JobExecution},
* and others will throw {@link JobExecutionAlreadyRunningException} (or
* timeout). There are no such guarantees if the {@link JobDao} does not
* respect the transaction isolation levels (e.g. if using a non-relational
* data-store, or if the platform does not support the higher isolation
* levels).
* method should block if another transaction is already executing it (for
* the same {@link JobIdentifier}). The first transaction to complete in
* this scenario obtains a valid {@link JobExecution}, and others throw
* {@link JobExecutionAlreadyRunningException} (or timeout). There are no
* such guarantees if the {@link JobDao} does not respect the transaction
* isolation levels (e.g. if using a non-relational data-store, or if the
* platform does not support the higher isolation levels).
* </p>
*
* @see JobRepository#findOrCreateJob(JobConfiguration, JobIdentifier)