Hi Ioannis, this works as expected. An @Alternative bean does not "disable" the original bean and so both observers should be notified. You're probably looking for specialization - see also 4.3. Specialization.
When trying to do the exact same thing scenario using alternatives enabled through beans.xml, only the observer of the enabled alternative is triggered.
Could you describe this scenario in more details? I don't think this should work. |