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

864 Commits

Author SHA1 Message Date
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
eb4991efe7 RESOLVED - BATCH-1066: StepParser updated to throw error if 'next' attribute and transition elements are both found. 2009-02-07 00:05:43 +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
4fd2cfc2db RESOLVED - BATCH-1061: reversed arguments to isLater() 2009-02-05 23:53:01 +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
447b1f0fbc BATCH-63: add more XSD meta data 2009-02-05 11:38:49 +00:00
dsyer
994f108303 Add more tooling support 2009-02-05 09:31:58 +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
35eea84747 Re-order parserContext calls to makes sure IDE gets info about source location 2009-02-04 16:27:02 +00:00
dsyer
5826cbb713 BATCH-1059: use milliseconds in date job parameter toString() 2009-02-04 16:26:08 +00:00
dsyer
cf875e0a38 Tidy up IDE callbacks in xml config 2009-02-04 15:50:31 +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
dsyer
c29895586b RESOLVED - issue BATCH-1054: Maven Build - incompatible bundle manifest version 
http://jira.springframework.org/browse/BATCH-1054
 2009-02-02 15:16:14 +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
b4a97d060f Add snapshots to BRITS plugin repositories 2009-02-01 13:27:51 +00:00
dsyer
b22c2bd44e Update MANIFEST.MF in bundle projects 2009-02-01 11:33:21 +00:00
dsyer
f47e8382d2 RESOLVED BATCH-1030: Added BatchStatus.INCOMPLETE. 2009-02-01 09:56:22 +00:00
dsyer
4f49b5816a Tweak javadocs 2009-01-30 09:17:49 +00:00
robokaso
c083ff07b4 REOPENED - BATCH-996: use default retryLimit == 1 (not 0) in *StepFactoryBean 
revert back to default retryLimit == 0 which was actually correct
 2009-01-29 13:20:20 +00:00
lucasward
81652cc6a1 BATCH-1007: Job and Step now have consistent attribute names for referencing the job repository, they're both 'job-repository' now. The docs have been updated accordingly. 2009-01-28 20:12:42 +00:00
lucasward
3785e8460f BATCH-985: Added documentation describing SkipListener behavior, also updated the incorrect javadoc. 2009-01-27 20:35:08 +00:00
robokaso
0e93bc7795 fix failing test 2009-01-27 17:49:38 +00:00
robokaso
9f9282a2a4 RESOLVED - BATCH-1032: Modify AbstractJobTests in test project to be able to launch FlowJob steps individually 
applied patch with some tweaks
 2009-01-27 17:42:45 +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
robokaso
a35786ec1d IN PROGRESS - BATCH-1010: StepFactoryBeans cleanup 2009-01-27 14:47:37 +00:00
robokaso
418e0baf95 IN PROGRESS - BATCH-1010: StepFactoryBeans cleanup 2009-01-27 14:28:33 +00:00
dsyer
983121e181 BATCH-1030: added unit test (commented out failed assertion) 2009-01-27 12:21:17 +00:00
robokaso
996926bc21 RESOLVED - BATCH-1025: Move PatternMatcher to infrastructure project 2009-01-27 11:42:37 +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
2898861782 BATCH-1004: improved error handling and documentation for step element 2009-01-27 04:21:31 +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
2672e055b8 RESOLVED - BATCH-1015: ItemListenerSupport should implement ItemProcessListener 
applied patch
 2009-01-26 15:09:20 +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
8bdccb2b0e RESOLVED - BATCH-1012: BatchListenerFactoryHelper: two if-statements, identical conditions 
patch applied
 2009-01-26 10:05:23 +00:00
robokaso
255885cc6b fix failing test (was assuming restartable=false by default) 2009-01-26 09:49:56 +00:00
trisberg
baff82b057 BATCH-1001: applied changes from the patch to set restartable to true as default 2009-01-23 15:49:12 +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
trisberg
b926a6401b BATCH-1006: appliad patch to change attributes to type xsd:string 2009-01-22 21:17:52 +00:00
trisberg
3867656484 BATCH-1008: removed sequencing requirements for the elements of a <tasklet> 2009-01-22 20:47:48 +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
trisberg
7397940ad7 BATCH-1003: applied patch to remove listeners element from tasklet 2009-01-22 15:45:55 +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
dsyer
971732d34f Add some Javadocs and change class visibility for row mapper. 2009-01-20 18:33:56 +00:00