[
https://issues.apache.org/jira/browse/CXF-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13938098#comment-13938098
]
Sergey Beryozkin commented on CXF-5576:
---------------------------------------
Having a dedicated servlet makes it simpler to have different context and
servlet paths for individual endpoints. Having it all defaulted is not
flexible, it is OK for some users but is not for others. For example, CXF OSGI
Blueprint transport is handy, but it is not that flexible and it catches the
registrations which are not meant for it. I honestly do no understand why
can't we have a little CXF servlet helper, it makes sense to me and it does not
interfere with other styles. Let get the bus auto-wired too, that is fine.
May be we will be able to do with CXFNonSpringServlet what we can now do with
CXFCdiServlet. But as I said, IMHO using CXFNonSpringServlet with CDI is not
really cool. CDI Servlet *is* a CXFNonSpringServlet, and in principle it can
accept servlet parameters affecting the CDI process or the initialization of
the beans created by CDI.
Sergey
> 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)
