org.springframework.core: public interface: Ordered

org.springframework.core
public interface: Ordered [javadoc | source] Interface that can be implemented by objects that should be orderable, for example in a Collection.

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.

Also see:

OrderComparator

org.springframework.core.annotation.Order

author: Juergen - Hoeller

since: 07.04.2003 -

Field Summary
int	HIGHEST_PRECEDENCE	Useful constant for the highest precedence value. Also see: java.lang.Integer#MIN_VALUE
int	LOWEST_PRECEDENCE	Useful constant for the lowest precedence value. Also see: java.lang.Integer#MAX_VALUE

Method from org.springframework.core.Ordered Summary:
getOrder

Method from org.springframework.core.Ordered Detail:
public int getOrder() Return the order value of this object, with a higher value meaning greater in terms of sorting. 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.

Method from org.springframework.core.Ordered Detail:

 public int getOrder()Return the order value of this object, with a
higher value meaning greater in terms of sorting.
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.