[
https://issues.apache.org/jira/browse/CXF-7643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16368148#comment-16368148
]
Romain Manni-Bucau commented on CXF-7643:
-----------------------------------------
John, there is no concurrent registration since servlet ones are standard and
must not be part of cxf. For these beans use the servlet integration of your
cdi container (weld or owb).
For the name: getname and @named lead to the same do you added named qualifier
without willing it. Cxf should probably remove all names - even on the bus -
and use @cxf but it is another issue for the bus.
More generally, never use default in a lib for a standard type which will
conflict with user or container code - a user can produce all beans you added
and you make him fail ;).
Having all beans without default qualifier and names by default sounds fine as
a fix.
> Ability to disable certain ContextResolved CDI Beans
> ----------------------------------------------------
>
> Key: CXF-7643
> URL: https://issues.apache.org/jira/browse/CXF-7643
> Project: CXF
> Issue Type: Improvement
> Components: JAX-RS
> Affects Versions: 3.2.2
> Reporter: Romain Manni-Bucau
> Priority: Trivial
>
> 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)
