Javadoc
Since archive detection logic is typically executed at a very early stage of deployment,
it is mainly heuristic. So some detectors can incorrectly recognize archives that they
actually don't support. e.g., take a war file inside an ear file. and asssume that the war file
contains some .jsp files. The archive detector responsible for handling the war
file could be fooled into thinking the ear file is a war file since it contains
jsp files, yet in reality, it only owns one of the sub archive bundled inside
the composite ear file.
To deal with such situations, each detector can specify a rank which can be used to order
the detectors. Since detectors can come from separate authors, rank of a detector must be
configurable in an installation.
The order in which detectors are used during archive detection is based on the rank. Lower the integer value
as returned by this method, earlier it is used during detection.