Bug 4762

Summary: SPEC - Property resolution
Product: jbatch Reporter: mminella
Component: sourceAssignee: cvignola
Severity: enhancement CC: issues
Priority: P5    
Version: 1   
Target Milestone: ---   
Hardware: All   
OS: All   

Description mminella 2013-03-11 14:21:58 UTC
Section states that "A property is considered defined once it is encountered by a top to bottom parse of the XML document."  I would expect to be able to resolve properties in any order in an XML document.  Since the document is not execution based (like the need to define a variable before we use it) with regards to properties I don't understand this limitation.
Comment 1 cvignola 2013-03-16 21:07:13 UTC
The document is not executable, true.  It is similar to Ant in that it directs an execution sequence.  And while I agree in principle there is no express purpose to require a property to be defined before it is used in substitution, we borrowed from the Ant model in the spec and in the RI with regard to this behavior. This is a rational way to prevent cycles.  I do not believe there is any important use case precluded by this choice.  Nor do I think usability or readability of the JSL is unduly compromised.