it is nice to define constants in the setup tag
<setup>
<set name="${startAt}" value="0" />
<set name="${stopAt}" value="5" />
<set name="${step}" value="1" />
</setup>
To make sure we can use these constants in every tag's property we could create a SQLUnitElement.
Each Handler would receive an SQLUnitElement instead of a Element.
SQLUnitElement would wrap an Element instance and
we could define a getAttributeValue(...) method and the constants would be automaticaly replaced.
This would provide a most centralized approach.
Any thoughts?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, I see what you mean, less occurences of the SymbolTable.getValue() noise. We should probably have the SQLUnitElement override the Element.getText() method as well.
-sujit
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
it is nice to define constants in the setup tag
<setup>
<set name="${startAt}" value="0" />
<set name="${stopAt}" value="5" />
<set name="${step}" value="1" />
</setup>
To make sure we can use these constants in every tag's property we could create a SQLUnitElement.
Each Handler would receive an SQLUnitElement instead of a Element.
SQLUnitElement would wrap an Element instance and
we could define a getAttributeValue(...) method and the constants would be automaticaly replaced.
This would provide a most centralized approach.
Any thoughts?
Hi Mario,
Yes, I see what you mean, less occurences of the SymbolTable.getValue() noise. We should probably have the SQLUnitElement override the Element.getText() method as well.
-sujit