Updates from the JSR 352 v1.0 Maintenance Release 20140214 Draft 2

* Per added section 9.3.2 - do not automatically make job properties available
  to artifacts when using @BatchProperty. Job properties are only available to
  artifacts when using the jobProperties substitution mechanism.

* Update tests to reflect changes
This commit is contained in:
Chris Schaefer
2014-02-28 11:11:23 -05:00
committed by Michael Minella
parent 319c751432
commit fe05e0daaf
5 changed files with 44 additions and 32 deletions

View File

@@ -6,6 +6,8 @@
<property name="jobPropertyName1" value="jobPropertyValue1"/>
<property name="jobPropertyName2" value="jobPropertyValue2"/>
<property name="step2name" value="step2"/>
<property name="filestem" value="postings"/>
<property name="x" value="xVal"/>
</properties>
<step id="step1" allow-start-if-complete="#{jobParameters['allow.start.if.complete']}">
@@ -92,6 +94,8 @@
<property name="batchletPropertyName2" value="batchletPropertyValue2"/>
<property name="annotationNamedBatchletPropertyName" value="annotationNamedBatchletPropertyValue"/>
<property name="nonexistentBatchletPropertyName" value="nonexistentBatchletPropertyValue"/>
<property name="infile.name" value="#{jobProperties['filestem']}.txt"/>
<property name="y" value="#{jobProperties['x']}"/>
</properties>
</batchlet>
</step>