[
https://issues.apache.org/jira/browse/CXF-7643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16368341#comment-16368341
]
Mark Struberg commented on CXF-7643:
------------------------------------
Agree.
Regarding the names: getName is for setting the EL name via programmatic
Bean<T>. So it must follow EL rules.
Another point: do you really want to expose the CXF Bus and other internals via
EL? Could easily become a security issue as a target for EL-injection hacks...
So I usually only expose beans to EL if I'm 100% certain that I will use them.
> 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)
