Hello Christian, I think you misread how CDI supports ordering in CDI extensions. Just for reference, I am talking about this part of CDI specification.
The notification order for observer methods within extensions follows the same ordering rule as defined in Observer ordering for non-extension observers. The priority of an observer method may be declared using the @Priority annotation.
This means that you can order observers for the same event within one extension, not in between several extensions. CDI TCK supports that as it has tests for what I described above, but no tests for what you try to achieve. The behaviour is IMO desirable as you can never know what other CDI extensions are in play from 3rd party libraries and shouldn't depend on that. In the same time you are free to enforce ordering on stuff happening in your own code. |