I'm afraid there is no specific order to the cacheMappings to begin with since it is a Properties instance, i.e. a Hashtable with no well-defined order of keys. Effectively, the behavior for overlapping path mappings is undefined there; we do not intend for this to be used with overlapping mappings.
That said, since the paths are not supposed to overlap to begin with here, there is no point in matching against all registered paths. For efficiency, we should proceed with the first match found. Nevertheless, this does not mean reliable ordering, just a more efficient match of a unique pattern.