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

526 Commits

Author SHA1 Message Date
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
dhgarrette
36f44c6ba7 BATCH-1011: Added test cases for default "status" attribute 2009-02-06 08:30:35 +00:00
dhgarrette
6e750b312d BATCH-1011: Added more conditions to unit tests (though some assertions are temporarily commented out because the status is not being set correctly by the end state). Also, fixed a bug in StepParser where the "on" attribute of the transition away from the end state was being set to the "on" attribute of the end state when it should have been "*". 2009-02-06 04:34:56 +00:00
dhgarrette
cae54225a8 BATCH-1011: 
spring-batch-2.0.xsd:
   * Renamed <stop/> to <pause/>
   * Added <fail/>
   
  StepParser.java
   * Added capabilities to parse <pause/> and <fail/>
   * Changed the semantics of the status= attribute so that it modifies the ExitStatus instead of BatchStatus.
   * BatchStatus is determined by the element (end, fail, pause)
   
  EndState.java
   * Added storage for ExitStatus in addition to the existing BatchStatus since both will need to be saved from the parser
 2009-02-05 20:42:31 +00:00
dsyer
ef4dba7590 RESOLVED - issue BATCH-1058: PlaceholderTargetSource doesn't always replace all placeholders 2009-02-05 09:02:01 +00:00
dsyer
ed60703fdf More tooling tweaks for namespace 2009-02-05 07:50:23 +00:00
dsyer
5826cbb713 BATCH-1059: use milliseconds in date job parameter toString() 2009-02-04 16:26:08 +00:00
dhgarrette
7487b4dfd2 BATCH-1053: Modified so that AbstractJob.getStep() returns null if the step is not found and Flow.getState() returns null if the state is not found. Javadocs and unit tests were updated to reflect this change. 2009-02-03 18:08:32 +00:00
dhgarrette
b09e1ece01 BATCH-1053: Updated javadocs to explain the behavior of getStep and getState if the step/state is not found. 2009-02-03 16:22:08 +00:00
dhgarrette
ee11f65556 BATCH-1053: Moved getStep() logic from AbstractJobTests to Job implementations. Added getStep(String) to AbstractJob. Added getState(String) to Flow. 2009-02-02 15:04:20 +00:00
dsyer
f47e8382d2 RESOLVED BATCH-1030: Added BatchStatus.INCOMPLETE. 2009-02-01 09:56:22 +00:00
dsyer
73bfca8bb8 CLOSED - issue BATCH-1024: FlowJob's start state should be the first state listed in the config 2009-01-27 16:05:25 +00:00
dsyer
983121e181 BATCH-1030: added unit test (commented out failed assertion) 2009-01-27 12:21:17 +00:00
robokaso
f4fa341233 RESOLVED - BATCH-1026: Rename ExitStatus.FINISHED to ExitStatus.COMPLETED 2009-01-27 11:38:26 +00:00
dsyer
8e1e352be4 RESOLVED - issue BATCH-1022: Chunk is not serializable but is wrapped by a Serializable ChunkRequest 
Added test for Serializable
 2009-01-27 10:58:30 +00:00
trisberg
e68d9a246a BATCH-1004: parser now uses the step name for bean references to step bean definitions 2009-01-27 02:20:06 +00:00
trisberg
c5da264dae BATCH-1016: applied patch promotionlistener-core-B-v2.patch 2009-01-26 18:44:30 +00:00
robokaso
d09691aad2 RESOLVED - BATCH-1016: Create listener to promote items from Step ExecutionContext to Job ExecutionContext 
applied patch and added unit test in core
 2009-01-26 11:11:59 +00:00
robokaso
255885cc6b fix failing test (was assuming restartable=false by default) 2009-01-26 09:49:56 +00:00
robokaso
92890da76e RESOLVED - BATCH-1009: Automatically register ItemReadListener, ItemWriteListener and ItemProcessListener 
applied patch + added autoregistration of skip and chunk listeners
 2009-01-23 15:04:38 +00:00
trisberg
9518ddc3f5 BATCH-1005: added start-limit and allow-start-if-complete attributes to <tasklet> 2009-01-22 22:38:16 +00:00
robokaso
a44f40a6cf REOPENED - BATCH-999: JobExecution ExecutionContext should not be persisted by Step? 
persist the job execution context only after step completion
 2009-01-22 17:13:53 +00:00
robokaso
6878eb0095 RESOLVED - BATCH-1002: Default behavior for a Job should be failure if a step fails 
applied patch
 2009-01-22 12:32:38 +00:00
robokaso
9c9fe8f6ca OPEN - BATCH-999: JobExecution ExecutionContext should not be persisted by Step? 
fix JobRepositoryUtilsTests
refactor internals of JdbcExecutionContextDao
 2009-01-20 13:55:39 +00:00
robokaso
c08bdad717 OPEN - BATCH-999: JobExecution ExecutionContext should not be persisted by Step? 
distinguish between save and update in ExecutionContextDao interface
initially save EC together with the execution it belongs to
 2009-01-20 13:32:14 +00:00
trisberg
784e640490 BATCH-997: changed test for setting exit status on contribution 2009-01-19 18:25:40 +00:00
robokaso
60e0b1692f RESOLVED - BATCH-997: EXIT_CODE and EXIT_MESSAGE out of synch for step 
persist the StepExecution.exitStatus properly in AbstractStep
 2009-01-19 11:09:12 +00:00
trisberg
0748880b13 BATCH-967: refeactoring the listener element checks and also added some tests 2009-01-15 17:22:20 +00:00
dsyer
ccd7a61ad8 BATCH-818: Add ivy meta data for Spring Build 2009-01-13 13:26:00 +00:00
robokaso
649abb69e8 RESOLVED - BATCH-983: Remove StepExecutionResourceProxy in favor of late-binding 
applied patches
 2009-01-13 12:46:04 +00:00
robokaso
e497499f40 OPEN - BATCH-990: Implement and test synchronizeStatus() in MapJobExecutionDao 
use upgradeStatus(..) instead of setStatus(..) in synchronizeStatus()
 2009-01-09 12:10:44 +00:00