This is a follow-on to
WFCORE-282 solution will not work for requests with address patterns
if the host named 'somename' is running a WFCORE version prior to 1.0.0.CR1 (or whatever release first has
In particular, it won't work with slaves running EAP 6.x.
The problem is with either of those address patterns the DC will send a request addressed to
to the slave, and the slave will not be able to handle it, as it won't have the
WFCORE-282 logic that lets it identify the relevant servers and send requests on to them.
Potentially this could be fixed by having the DC detect these patterns and not call
, instead adding a step to read the server child names from /host=somename and then call /host=somename/server=a, /host=somename/server=b, etc.