[
https://issues.apache.org/jira/browse/CXF-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941667#comment-13941667
]
Andriy Redko commented on CXF-5576:
-----------------------------------
Hey guys,
The extension reference from CXFCdiServlet is gone :-) I am looking into these
issues:
- how to support customization
- how to make more CXFCdiServlet CDI-ish to cover more use cases
With respect to beans.xml, as far as I understand, the new beans cannot be
added to context there (I have investigated this possibility when started to
work on the issue). The beans.xml can control alternatives, interceptors,
decorators, scan locations (exclude-only) and basic discovery modes. I
consulted the spec as well and it seems to be the case.
Thanks.
Andriy
> Initital support for CDI integration
> ------------------------------------
>
> Key: CXF-5576
> URL: https://issues.apache.org/jira/browse/CXF-5576
> Project: CXF
> Issue Type: Improvement
> Components: Core
> Affects Versions: 3.0.0
> Reporter: Andriy Redko
> Assignee: Andriy Redko
> Labels: cdi
> Attachments: weld-one-jar.zip, weld-one-war.zip
>
>
> A per section 10.2.3 Context and Dependency Injection (CDI) of JAX-RS 2.0
> specification, in a product that supports CDI, the implementations MUST
> support the use of CDI-style Beans as root resource classes, providers and
> Application subclasses. Providers and Application subclasses MUST be
> singletons or use application scope.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
