[cdi-dev] Ordering of AfterTypeDiscovery#getAlternatives() et al

Jozef Hartinger jharting at redhat.com
Mon Dec 22 03:23:08 EST 2014


On 12/20/2014 11:26 AM, Mark Struberg wrote:
> Hi!
>
> If I have a
>
>
> @Priority(100)
> public class MyAlternative implements Foo ..
>
> and
>
>
> @Priority(101)
> public class ABetterAlternative implements Foo ..
>
>
> Then ABetterAlternative will finally be chosen.
>
> This ordering can be changed via AfterTypeDiscovery#getAlternatives().
>
> But the spec only says "returns the ordered list of enabled alternatives for the application.."
>
> But it does NOT define in which sorting this list is ordered ;)
>
> In OWB we hat the 'most important' alternative come first. It seems in Weld it is the other way around.
What sorting do you use for interceptors and decorators?
>
> I have no problem with changing this in OWB, but I would like to get this clarified in our JavaDocs and spec.
Agreed. Go ahead and file an issue.
>
> LieGrue,
> strub
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
>
> Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.



More information about the cdi-dev mailing list