Uploaded image for project: 'CDI Specification Issues'
  1. CDI Specification Issues
  2. CDI-201

Reflect BeanAttributes within validation rules

    XMLWordPrintable

    Details

    • Affects:
      Release Notes

      Description

      For example:

      1)

      The spec says:

      Each child <class> element must specify the name of an alternative bean class. If there is no class with the specified name, or if the class with the specified name is not an alternative bean class, the container automatically detects the problem and treats it as a deployment problem.

      Since that "alternative" attribute of a bean can be altered by a portable extension in the ProcessBeanAttributes phase, the specification should instead require for each class listed in the <class> element, each bean that defines the class as its bean class is an alternative.

      2)

      If Y has a name and X declares a name explicitly, using @Named, the container automatically detects the problem and treats
      it as a definition error.

      The specification should abstract from @Named, since the ProcessBeanAttributes enables an extension to set a bean name without using @Named

      Likely, there are other similar issues.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              pmuiratbleepbleep Pete Muir
              Reporter:
              rhn-engineering-jharting Jozef Hartinger
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: