In Resteasy 2 it was possible for a sub-resource locator to execute successfully
even when there was also a sub-resource with the same uri. This was incorrect
behavior according to the specification. This issue was fixed in Resteasy 3.
It would be helpful to customers upgrading from Resteasy 2 to 3 to having a
warning msg for this situation.
It is desirable to have this fix put in the Resteasy version that does into EAP 7.x.