Spring/spring-batch
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
2,898 Commits 16 Branches 0 Tags
b4375aae21189baba6a5fba1fc5bc335c5eb7ac4
Commit Graph

556 Commits

Author SHA1 Message Date
dhgarrette
b4375aae21 BATCH-1118: Modified StepListenerFactoryBean so that listener methods specified via annotations or the metaDataMap are checked for correct signatures. This allows incorrect methods to fail eagerly. For added flexibility, methods are also allowed if they do not specify any parameters. 2009-03-07 07:16:06 +00:00
dhgarrette
78c88afce0 BATCH-1125: Modified NoWorkFoundStepExecutionListener so that it will fail the step. Removed unused NoWorkFoundException. 2009-03-06 23:51:53 +00:00
dsyer
bb9fd79bf1 Rationalise writer exception hierarchy 2009-03-06 08:24:12 +00:00
dsyer
cdc112c964 Listener to copy parameters into execution context so that local step can be configured identically to remote step in a partition. 2009-03-06 08:05:30 +00:00
dsyer
691f324873 Switch to String[] for dependency injection. 2009-03-06 08:04:21 +00:00
dhgarrette
204aa1fe9e RESOLVED - BATCH-1119: Updated chunk recovery procedure in FaultTolerantChunkProcessor so that the AfterWrite listener method is called even if no exception is thrown during throttling. 2009-03-06 03:17:17 +00:00
lucasward
6f9fb36157 BATCH-1114: Moved FlushFailedException into support.transaction 2009-03-04 04:54:25 +00:00
dsyer
9a3e55e58e RESOLVED - issue BATCH-570: Job.getSteps() does not need to be exposed in the interface 
Added getStepNames() to StepLocator.
 2009-03-03 19:12:14 +00:00
dsyer
9fa730100c OPEN - issue BATCH-1108: Add composite ItemWriter/Processor based on Classifier 
Move test case over from core as well
 2009-03-03 12:23:59 +00:00
dsyer
998f6f592e OPEN - issue BATCH-1108: Add composite ItemWriter/Processor based on Classifier 
First draft of classifier features added.  Also refactored MethodInvoker abstraction into infrastructure.
 2009-03-03 11:55:03 +00:00
dsyer
b215feb9e8 RESOLVED - issue BATCH-1111: ChunkListener called before WriteListener 2009-03-02 17:44:17 +00:00
dsyer
b1967f046a BATCH-1107: it's not the OS it's he timezone of the build server! 2009-02-28 12:59:07 +00:00
dsyer
b0e19a9942 BATCH-1107: apparently new Date(0L) is not 1970/01/01 on all operating systems! 2009-02-28 12:14:44 +00:00
dsyer
eb44c0d493 BATCH-1107: add PropertyEditor support to placeholder resolution to deal with Dates 2009-02-28 12:01:58 +00:00
dsyer
da522c20e0 BATCH-1103: Bad meta data for listener methods fixed 2009-02-25 19:03:24 +00:00
dsyer
8bd116006c RESOLVED - issue BATCH-1102: Classes with "listener" annotations should be auto-registered 
Added convenience methods to *ListenerFactoryBean and then used in *StepFactoryBean
 2009-02-25 16:03:39 +00:00
dsyer
044a91eddf BATCH-1103: Added partitioning sample 2009-02-25 12:31:13 +00:00
dsyer
b5450ddc67 RESOLVED - issue BATCH-1093: Make AbstractJobTests.makeUniqueJobParameters() public 
RESOLVED - issue BATCH-1096: Add late binding to some io samples 
RESOLVED - issue BATCH-1087: ClassPathXmlJobRegistry does not accept patterns for resources 
RESOLVED - BATCH-1098: added test for @AfterWrite in FaultTolerantChinkProcessorTests
 2009-02-24 15:34:49 +00:00
dsyer
cc47fa82d9 FIXED - issue BATCH-1092: Fix naming conventions for exit status in <end/> 
Changed ExitSTatus aggregation rule so that custom codes come out on top.
 2009-02-23 18:17:52 +00:00
dsyer
95bbf6d0f0 OPEN - issue BATCH-937: Make sure JobRepository can be proxied 
Plus fix error with stax config in tiger profile
 2009-02-23 15:19:05 +00:00
dsyer
cb0955ad1b BATCH-1011: tidy up FlowExecutionStatus name access 2009-02-18 19:10:13 +00:00
dsyer
7a8598e244 RESOLVED - issue BATCH-1086: JdbcJobExecutionDao.getRunningJobExecutions() ignores jobName 
Change query to use job name.
 2009-02-18 12:54:08 +00:00
dsyer
ae275e8f5d PassThrough* 2009-02-18 08:29:10 +00:00
dsyer
57cf2b1c0b BATCH-1087: add test case 2009-02-18 08:28:06 +00:00
dsyer
e84c94b307 BATCH-1087: use Resource[] for setting classpath resources 2009-02-18 08:22:35 +00:00
dsyer
365fd46744 RESOLVED - issue BATCH-1011: Need distinction between "stop" and "end" transitions? 
Push JobExecution status update out of the EndState and back into FlowJob (via FlowExecutor).
 2009-02-17 13:11:33 +00:00
dsyer
3836cd9597 RESOLVED - issue BATCH-1050: SimpleJobExplorer doesn't retrieve StepExecutions of running JobExecutions using MapStepExecutionDao 
Make StepExecutionDao interface clearer from the point of view of adding step executions to a JobExecution.
 2009-02-17 09:00:11 +00:00
dhgarrette
3502c0f14a BATCH-1011: added test case for a second launch 2009-02-16 23:32:07 +00:00
dhgarrette
bc679464fc BATCH-1076: added test case for restart back on a step that failed. 2009-02-16 23:26:33 +00:00
dsyer
ceccb5762e RESOLVED - issue BATCH-1050: SimpleJobExplorer doesn't retrieve StepExecutions of running JobExecutions using MapStepExecutionDao 
Added step executions explicitly in the Dao.
 2009-02-16 16:02:44 +00:00
trisberg
46e67ab1cb BATCH-949: renamed mapper property to rowMapper 2009-02-16 14:22:16 +00:00
robokaso
e40aab476a REOPENED - BATCH-618: DefaultJobParametersConverter does not parse parameters of type double 
handle round doubles correctly
 2009-02-15 22:15:58 +00:00
dsyer
9391d6f471 BATCH-1011: add nesting to FlowExecutor so that SplitState can detect a nested flow 2009-02-15 17:31:53 +00:00
dsyer
7533f90480 BATCH-1011: Refactor BatchStatus again so that FAILED has the same meaning as before (1.1.x etc.) and ABANDONED is introduced to signify a step that failed but does not need to be replayed on restart (formerly known as INCOMPLETE). 2009-02-15 10:59:44 +00:00
dhgarrette
fa56955f8d BATCH-1064: Changed BatchStatus.FAILED to BatchStatus.INCOMPLETE where necessary 2009-02-14 19:34:51 +00:00
dhgarrette
32d34d78d2 BATCH-1076: fixed unit test error 2009-02-13 20:54:01 +00:00
dhgarrette
c92179d8d3 BATCH-1076: Cleaned up and renamed test 2009-02-13 08:24:25 +00:00
dhgarrette
7aeb6301d1 BATCH-1076: Created new test for <stop> that restarts on the last step executed. 2009-02-13 07:56:33 +00:00
dhgarrette
b2e0fe655a Collapsed two tests into one. 2009-02-13 07:26:31 +00:00
dhgarrette
f562b01d6e BATCH-1065: Added check to ensure that a transition from an EndState does not have a "pattern" associated. EndState transitions must always be universal. 2009-02-13 06:37:08 +00:00
dhgarrette
73ed78da31 BATCH-1065: Moved StateSupport up one package level to be accessible to FlowJobTests 2009-02-13 06:28:02 +00:00
dhgarrette
b04841548e BATCH-1064: Switched the semantics of INCOMPLETE and FAILED. Combined INCOMPLETE with STOPPED. INCOMPLETE jobs and steps can be restarted while COMPLETED and FAILED jobs and steps cannot. 2009-02-13 06:12:28 +00:00
trisberg
766941104f BATCH-1034: regsitering StepScope if it is not already registered 2009-02-11 22:21:46 +00:00
robokaso
b235aa75aa IN PROGRESS - BATCH-1010: StepFactoryBeans cleanup 
don't treat retryable exceptions automatically as skippable (did it ever make sense?)
cleanup misleading and redundant test configurations
 2009-02-10 12:54:48 +00:00
trisberg
d3396a3fa7 BATCH-1013: split the <step> elements name attribute into id and ref attributes 2009-02-10 04:52:03 +00:00
dsyer
74c167f34c BATCH-1053: refactor State and AbstractJob to remove cycle 2009-02-09 13:59:28 +00:00
dhgarrette
b2a31fe740 BATCH-1067: updated .springBeans 2009-02-08 19:52:45 +00:00
dhgarrette
7c4953f2be BATCH-1067: 
* FlowJob waits until the Job is finished before updating BatchStatus and ExitStatus.  This is required so that individual flows in a split don't modifify the JobExecution prematurely.
* Removed FlowExecution$Status and replaced it with FlowExecutionStatus, a class that holds both a BatchStatus and an ExitStatus.  This is required by the EndState because the handle() method needs to be able to return both BatchStatus and ExitStatus so that they can be applied correctly to the JobExecution when ending the job.
 2009-02-08 18:32:03 +00:00
dhgarrette
d306c418fa BATCH-1011: Added new test case to show 'pause' element's ability to skip a FAILED step on restart. 2009-02-07 15:56:47 +00:00
dhgarrette
dfb78ff0ca BATCH-1011: 
* Moved logic for updating JobExecution status based on last StepExecution from AbstractJob to SimpleJob because it does not apply to FlowJob.
  * A job now can have a status different from any of its steps.  For example, the following job will be COMPLETED while the step will be FAILED:
    <step id="failingStep">
       <end on="FAILED" /> 
    </step>
* Added error checking to StepParser to make sure the same pattern does not appear more than once.
* Modified EndState.handle() so that the ExitStatus is only updated if BatchStatus is updated.
  * If a job contains a <split> such that there is more than one EndState reached, the Job's status will be the highest precedence of all the statuses.  For example, the following job will be FAILED:
    <split id="split1">
      <flow>
        <step name="failingStep"/>
      </flow>
      <flow>
        <step name="step1"/>
      </flow>
    </split>
* If a step has no transitions defined, then the default will be:
    <fail on="FAILED" />
    <end on="*" />
 2009-02-06 23:13:21 +00:00