[
https://issues.apache.org/jira/browse/CXF-7643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16365503#comment-16365503
]
Romain Manni-Bucau commented on CXF-7643:
-----------------------------------------
Hi John, even meant for the app server it is an issue and will lock users in
the future. But agree for now servlet part is blocking and a workaround for
partial CDI environments so should be an activable toggle not on by default at
the minimum. Now it is not ProcessBean but ProcessSyntheticBean. Issue is also
it is added in AfterBeanDiscovery and therefore is not that portably
rewrittable. Also it should just not be rewritten since in the order of
precedence CXF should check if they already exist and if so not add them (ie
CXF can customize servlet or CDI but not the opposite in terms of dependencies).
> [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)
