[
https://issues.apache.org/jira/browse/CXF-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937739#comment-13937739
]
Andriy Redko commented on CXF-5576:
-----------------------------------
Hi Christian,
Thanks, I will work on that (should be easy, we know how to do that already).
With respect to getting rid of servlet, I am not sure we can do that. The
problem is not to make it CDI discoverable (we can do that f.e. with
@WebServlet) but the path is should be configured with: we cannot hardcode it
(unless you see the way to overcome that). As such, we cannot make this servlet
to be fully CDIish, we should allow people to map it to whatever they want. BUT
eventual code would be as easy as BlueprintServlet: ask a container for a bus
and that's it. Make sense to you?
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)
