AggregatingLocator.locate should try the next locator if the first one fails

This stupid bug was caused in "e6812a5ae00dad17827a85a0150a252fd5b43488" during
a terminology change.