The documentation on wrapper.script.<n>.<state>
specified that "For the same state execution order is the alpha numeric order of <n>
". Actually scripts appear to be executed in no particular order that changes when the config is modified.
The configuration entries are indeed processed using an ArrayList
with the Collections.sort()
, but StateChangeListener
objects created for scripts are stored in a HashSet
and processed using HashSet
's iterator, so the order is lost which seems to be the culprit
thanks for reporting. will be resolved with release 13.11