[
https://issues.apache.org/jira/browse/CXF-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937355#comment-13937355
]
Andriy Redko commented on CXF-5576:
-----------------------------------
Hey guys,
I would agree with Sergey: we may not look into one strategy but several of
them. The one we have right now is servlet-based and it might be harder to
create the configurable HTTP endpoints without it. But I will experiment a bit
in this direction as well so to minimize direct interactions with container.
If I understood Christian correctly, we may shift the container interaction (if
needed) into the bus itself (let say CdiBus). It sounds also as an option we
can try to look at.
I guess we can introduce CdiResourceExtension as well and work over it. I will
try that.
Thanks guys!
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)
