Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-2658

Synthetic alternatives registered via WeldBeanConfigurator do not trigger ProcessBean event

    XMLWordPrintable

    Details

      Description

      Can be reproduced by slight modification in CustomBeanPriorityTest. Alter the extension to also observe ProcessBean and this will never trigger.

      The reason is that for ProcessBean we check if the given bean is enabled and the newly added bean will fail this check because ModuleEnablement doesn't yet recognize this bean.

      The Beans#isBeanEnabled() check could perhaps be extended to contain a special check for synth alternatives.

        Attachments

          Activity

            People

            Assignee:
            manovotn Matěj Novotný
            Reporter:
            manovotn Matěj Novotný
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: