| Hi Martin, I think it is stated in 5.1.2. Enabled and disabled beans that only the selected alternative beans are considered as enabled. In combination to 10.3 Observer Resolution which states that the resolved observer methods should belong to enabled beans, I would expect only the selected alternatives to receive events. In any case, it is understood that this is the expected behavior. Here is my clarification about the discrepancy that I identified. When I define two alternative beans that both define an observer method for the same event type, and I select one bean class using beans.xml tags (not using @Priority), only the selected bean receives the event. This contradicts the above case. I do not have a unit test, but let me know if my description is still not clear enough, so I create a unit test, as well as work on a possible fix/patch ![]() |