[EXTVAL-65] invocation order mechanism

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.2.1, 1.2.2, 1.1.1, 1.1.2
• Fix Version/s: 1.2.3, 2.0.3, 1.1.3
• Component/s: Core
• Assignee: Unassigned
• Reporter: Gerhard Petracek
• Created: 14/Oct/09 00:38
• Updated: 23/Mar/10 10:52
• Resolved: 15/Oct/09 17:16

Description

for some artifacts it makes sense to define the order of execution when it comes to add-ons which have to extend extval in a very special way. that allows to force an execution order independent of the registration order.

@InvocationOrder ... marks an artifact with a given order
@InvocationOrderSupport... marks interfaces (instances of classes implementing these interfaces will be sorted internally)

suggested ranges:
negative values for very special cases
0-49 for custom artifacts which should have the highest priority
50-99 for add-ons which provide artifacts which should have a higher priority than the default artifacts
100-999
1000+ for custom artifacts

a priority should be unique within one artifact-type - that means:
if a name-mapper has priority 100, it's ok that an exception-interceptor also has priority 100.
but a 2nd name-mapper shouldn't have priority 100 (if so - the order depends on the registration order)