[
https://issues.apache.org/jira/browse/CXF-7643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16404157#comment-16404157
]
ASF GitHub Bot commented on CXF-7643:
-------------------------------------
rmannibucau opened a new pull request #393: CXF-7643 ensure CDI extension
defaults are CDI compliant
URL: https://github.com/apache/cxf/pull/393
This PR tries to make defaults of the CDI extension better, here are the
changes:
1. if it detects OWB-web or weld-web it deactivate default context beans for
HttpServletRequest and ServletContext
2. it observes beans to detect the types conflicting with "auto" context
beans
3. it fires the extension and exposes the list of exclusion to let
integration layers configure it properly if 1/2 defaults are not enough
4. when it adds context beans it removes @Default from the ones which are
found with 1/2/3 - but it keeps it with the cxf specific qualifier if needed
(best practise being to use this classifier for internal/extensions needs)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Ability to disable certain ContextResolved CDI Beans
> ----------------------------------------------------
>
> Key: CXF-7643
> URL: https://issues.apache.org/jira/browse/CXF-7643
> Project: CXF
> Issue Type: Bug
> 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)
