[
https://issues.apache.org/jira/browse/CXF-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937300#comment-13937300
]
Sergey Beryozkin commented on CXF-5576:
---------------------------------------
Yes re other servlets, but having an ability to use a Servlet allows us to
control the *servlet patterns*. We lose the servlet we immediately have a
problem of how to set it up elsewhere. I don't think having a simple CDI
servlet helper is interfering with anything else.
Re SOAP/JMS : I don't see why the servlet will need to be used in that case:
have users do one liner which is done in the CDI servlet without using the
servlet :-). If we have no HTTP endpoint then neither CXFCDIServlet nor
CXFNonSpringServlet are appropriate.
> 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)
