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

@Veto and ProcessAnnotatedType

    XMLWordPrintable

Details

    • Clarification
    • Resolution: Duplicate
    • Critical
    • None
    • 1.1.EDR
    • Concepts, Packaging and Deployment
    • None

    Description

      currently the spec. specifies:
      "The container must fire an event for each Java class or interface it discovers in a bean archive, and for annotated type added by BeforeBeanDiscovery.addAnnotatedType(), before it reads the declared annotations."

      that's ok for cdi 1.0.
      however, if @Veto gets added to cdi 1.1, we need a clarification here.
      the internal implementation via a std. cdi doesn't make sense because other extensions still get the corresponding ProcessAnnotatedType event.
      -> Annotated types with @Veto (or as suggested at CDI-50: @Unmanaged or @Exclude) shouldn't lead to a ProcessAnnotatedType event.

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users CDI-50 Ability to veto beans, both unconditionally and based on classes visible

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              struberg Mark Struberg (Inactive)
              gpetracek Gerhard Petracek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: