The actual order can be interpreted as prioritization, with the first object (with the lowest order value) having the highest priority.
Note that there is a 'priority' marker for this interface: PriorityOrdered . Order values expressed by PriorityOrdered objects always apply before order values of 'plain' Ordered values.
|int||HIGHEST_PRECEDENCE||Useful constant for the highest precedence value.|
|int||LOWEST_PRECEDENCE||Useful constant for the lowest precedence value.|
|Method from org.springframework.core.Ordered Summary:|
|Method from org.springframework.core.Ordered Detail:|
public int getOrder()
Normally starting with 0 or 1, with #LOWEST_PRECEDENCE indicating greatest. Same order values will result in arbitrary positions for the affected objects.
Higher value can be interpreted as lower priority, consequently the first object has highest priority (somewhat analogous to Servlet "load-on-startup" values).
Note that order values below 0 are reserved for framework purposes. Application-specified values should always be 0 or greater, with only framework components (internal or third-party) supposed to use lower values.