[
https://issues.apache.org/jira/browse/CXF-7643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16368085#comment-16368085
]
John D. Ament commented on CXF-7643:
------------------------------------
So, it's on purpose that {{@Default}} is in the qualifiers, so that a user
doesn't need to use a qualifier. However, I also added {{@ContextResolved}} to
the qualifiers, to avoid being the only one to produce it. As I understand it
though, the issue really comes in when trying to product the {{javax.servlet}}
beans, since those may come from other specs (e.g. on a full app server its
provided by the container, and I suspect OWB servlet module is also producing
them). If I had to guess, neither of those are adding a qualifier, so really
your issue is that multiple components are all trying to produce the same bean.
I think where we were leaning on list was to introduce a config property on
what to turn on or off, which could come from the Bus.
As far as {{getName()}} goes, I'm not sure I understand your point. AIUI
{{getName()}} is for {{BeanManager.getBeans(String)}} and has nothing to do
with {{@Named}}
> [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)
