Details

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  struberg Mark Struberg
                  Reporter:
                  gpetracek Gerhard Petracek
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: