[
https://issues.apache.org/jira/browse/DELTASPIKE-1143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mark Struberg resolved DELTASPIKE-1143.
---------------------------------------
Resolution: Won't Fix
This is a nice idea, but the effort is way too high.
Extensions do not really have a notion of BDA. So they don't really know from
which jar the scanned AnnotatedType is coming from. That means that we would
really need to configure all the allowed/disallowed packages via Strings. And
this is really ugly and expensive.
> Implement an extension to veto AnnotatedType without a bean defining
> annotation
> -------------------------------------------------------------------------------
>
> Key: DELTASPIKE-1143
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-1143
> Project: DeltaSpike
> Issue Type: New Feature
> Components: Core
> Reporter: Martin Kouba
> Assignee: Mark Struberg
> Priority: Major
>
> This would essentially replace the need for a new bean discovery mode (see
> also CDI-420). The difference is the extension would be enabled globally and
> bean discovery mode is defined per bean archive.
> The extension should be configurable so that it was possible to exclude
> packages/classes from processing.
> * https://issues.jboss.org/browse/CDI-420
> *
> http://transcripts.jboss.org/channel/irc.freenode.org/%23cdi-dev/2016/%23cdi-dev.2016-05-04.log.html#t2016-05-04T13:16:21
> * http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#bean_defining_annotations
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
