| Re: [config-dev] What priority means in Jakarta |
Hi, Yes, it mentions highest priority, but it doesn’t say how the highest priority is calculated. If we check the javadoc for javax.enterprise.inject.spi.AfterTypeDiscovery#getAlternatives: the list of enabled alternatives for the application, sorted by priority in ascending order The spec doesn’t seem to be clear to how Alternatives execute, so lets look into Decorators: Decorators with the smaller priority values are called first. And the javadoc for javax.enterprise.inject.spi.AfterTypeDiscovery#getDecorators: the list of enabled decorators for the application, sorted by priority in ascending order. So I assume that there is some consistency here and the order returned in this method calls is also the executing order (at least for Decorators, I’ll have to confirm for Alternatives). And Observers: Observers with smaller priority values are called first. Maybe there are cases where CDI is doing the opposite (biggest priority number), but it seems that the majority of cases is lowest priority number = first execution. The interesting thing is that the annotation spec leaves this open to the consumer: The effect of using the Priority annotation in any particular instance is defined by other specifications that define the use of a specific class. But this is not really a good thing in my opinion. As we were discussing the way that priority order should be consistent across all Jakarta platform and not defined at each specification, or we end up with this mess where we never know how it works for each case. Cheers, Roberto
|