Bug 4259

Summary: chunk properties naming
Product: jbatch Reporter: geofjamg
Component: sourceAssignee: cvignola
Status: CLOSED FIXED    
Severity: enhancement CC: issues
Priority: P5    
Version: 1   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard:

Description geofjamg 2012-11-06 22:58:37 UTC
Instead of having a specific property naming pattern for chunk artifacts (< artifact-name :property-name>) why not just using a child element of the chunk element for each artifact (reader, processor, writer) ? I think it would be clearer and more consistent with the rest of the job xml specification.

Example:
<chunk>
   <reader ref=”MyReader”>
       <properties>
           <property name="filename" value="/tmp/infile.txt" >
       </properties>
   </reader>
   <processor ref=”MyProcessor”/>
   <writer ref=”MyWriter”>
       <properties>
           <property name="filename" value="/tmp/outfile.txt" >
       </properties>
   </writer>
</chunk>
Comment 1 cvignola 2012-11-19 13:17:37 UTC
Good idea. It solves the problem we've been wrestling with concerning how to assign properties to each artifact:  reader, processor, writer.   Originally, we patterned off Spring Batch's chunk element, which uses elements to specify those  three artifacts.   But having separate elements works better here.  I think this is a good change.