[
https://issues.apache.org/jira/browse/DELTASPIKE-817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerhard Petracek updated DELTASPIKE-817:
----------------------------------------
Fix Version/s: 1.4.3
> API and Core contain types recognized as managed beans but declaring an
> illegal bean type
> -----------------------------------------------------------------------------------------
>
> Key: DELTASPIKE-817
> URL: https://issues.apache.org/jira/browse/DELTASPIKE-817
> Project: DeltaSpike
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.2.0
> Reporter: Martin Kouba
> Assignee: Mark Struberg
> Priority: Minor
> Fix For: 1.4.3
>
>
> API and Core artifacts contain some types which are recognized as managed
> beans but in the same time they declare an illegal bean type, namely a
> parameterized type that contains a wildcard type parameter:
> * org.apache.deltaspike.core.util.Annotateds$AnnotatedCallableComparator
> * org.apache.deltaspike.core.util.Annotateds$AnnotatedConstructorComparator
> * org.apache.deltaspike.core.util.Annotateds$AnnotatedFieldComparator
> * org.apache.deltaspike.core.util.Annotateds$AnnotatedMethodComparator
> * org.apache.deltaspike.core.impl.exception.control.ExceptionHandlerComparator
> The spec is not clear what should happen in this case (although it would make
> sense to just ignore the type and log some warning), see also the
> corresponding issue:
> https://issues.jboss.org/browse/CDI-495
> I believe these beans should either be completely excluded from scanning
> (vetoed, etc.) or should have their set of bean types restricted.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
