With our int based approach if someone picks 100 and someone later comes and takes 101, there's no getting between them.
I would support @Priority for really all listener-type APIs we have across all specs, but I think we should push for a change from int likely to double (the only safe cast from int).
That, or Stuart's suggestion sounds like a good idea.
Two additional things to consider here:
2. In Jakarta Security we have IdentityStores which can be called in a given order (set by a priority as well). However, by registering a single class (fully optional), the user is in full control of this order programmatically, meaning they can effectively veto any store, or have them called in any order.
Perhaps this approach can be considered to be adopted universally, or at least in this case here by Servlet.
Kind regards,
Arjan Tijms
_______________________________________________
servlet-dev mailing list
servlet-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/servlet-dev
