[
https://issues.apache.org/jira/browse/CXF-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13944612#comment-13944612
]
Sergey Beryozkin commented on CXF-5576:
---------------------------------------
Hi Andriy
Actually, re this example, this reminds me we need to fix the extension code,
we can't have Application & service resources/providers separately, in the
tests we have an empty Application which is not correct :-). It is either
Application that creates services and providers or services/providers are
discovered independently...
Re this approach: IMHO it is not really CDI :-) and we need to seek how it is
done with CDI, otherwise why would people do CDI instead of Blueprint/Spring if
it is not possible to set the bean properties ?
May be we can consider wrapping up this issue and create a new one
specifically to do with the customizations ?
The one pending issue I think here is that if we really want a portable CDI
servlet which will work for all the frontends then should we move a text
resource specifying the extension to the JAX-RS frontend ? Not really sure
though
Thanks, Sergey
Thanks, 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)
