Bugzilla – Bug 4762
SPEC - Property resolution
Last modified: 2013-03-16 21:07:13 UTC
Section 220.127.116.11 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.
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.