[
https://issues.apache.org/jira/browse/CXF-7643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16367552#comment-16367552
]
Mark Struberg commented on CXF-7643:
------------------------------------
I fell over this as well.
CXF-3.2.2 out of the box collides with CDI-2 containers, giving
AmbiguousResolutionException on each of them.
There are also other smallish flaws.
E.g. implementing getName() is intended to be a for @Named EL name. Having
spaces in there contradicts the EL spec.
Let's start the other way around: I'm shure there was a reason why this class
got added. So what is the use case to be solved?
> [jaxrs][cdi] Remove ContextProducer beans
> -----------------------------------------
>
> Key: CXF-7643
> URL: https://issues.apache.org/jira/browse/CXF-7643
> Project: CXF
> Issue Type: Task
> Affects Versions: 3.2.1
> Reporter: Romain Manni-Bucau
> Priority: Blocker
>
> ContextProducerBeans are added for all @Context fields.
> This is not in the spec so it must use a custom qualifier only and not leak
> @Default support for all context types.
> Currently it fails with servlet beans which are supported by any CDI@servlet
> container and already provided as required by the spec which leads to 1. an
> inconsistent bean being deployed 2. an ambiguous resolution.
> Side note: this feature can stay as an activable thing but not as a default
> for the mentionned reasons.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
