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

Public fields in extensions should not be allowed

XMLWordPrintable

    • Icon: Clarification Clarification
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • 1.1.PFD
    • Portable Extensions
    • None

      Since the container must provide an @ApplicationScoped bean for every extension and since a proxy must be injected into injection points requesting this bean, it should be clear that extensions should not be allowed to have public fields. The spec doesn't specify this explicitly, but it should - like it does for non-dependent managed beans.

      The container should treat this as a definition error, otherwise people may end up accessing these public fields of extensions and getting weird errors.

      See also WELD-1474

              Unassigned Unassigned
              marko.luksa@gmail.com Marko Luksa (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: