[#RIFE-286] RIFE should support @Priority annotations for method and field annotations on elements

RIFE

RIFE should support @Priority annotations for method and field annotations on elements

Created: 29/Jun/06 12:50 AM Updated: 26/May/08 02:04 PM

Component/s:

None

Affects Version/s:

1.5

Fix Version/s:

1.5

Original Estimate:

Unknown

Remaining Estimate:

Unknown

Time Spent:

Unknown

Scale:

Bite-sized

Description

« Hide

Since it's not possible to retrieve the methods of a class in a predictable order, an artificial element needs to be introduced to make it possible for certain annotations to always come before others. Otherwise submissions can't be declared before their parameters, for example. Methods and fields that current position annotation should be analyzed first. Those without any position information come afterwards.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Geert Bevin [29/Jun/06 01:14 AM]

The position annotation should support structured values so that it's not simply a numeric sequence. Instead of having 1, 2 ,3, 4, 5 ... one should be able to do 1, 1.1, 1.2, 1.3, 2, 2.3, 2.4, 3 with 1 < 1.* < 2 < 2.* < 3. This makes it easy to add additional elements inside a section without having to renumber everything. Concretely, this allows submissions to for example be positioned as 1, 2,3 and parameters as 1.1, 1.2, ...

[ Permlink | « Hide ]

Geert Bevin [08/Jul/06 12:54 PM]

Used @Priority annotation. Methods without priority always come before the ones that have one.