[
https://issues.apache.org/jira/browse/CXF-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937712#comment-13937712
]
Christian Schneider commented on CXF-5576:
------------------------------------------
Hi Andriy,
that sounds good to me. Then the extension should be able to publish the
endpoints directly. We then should be able to either use the normal
CXFNonSpringServlet or perhaps create a very simply extended servlet that can
get the cxf bus injected using CDI but does not do anything more.
I think in OSGi we should not even need a servlet as all endpoints should be
available on the default cxf OSGi based servlet.
Christian
> 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)
