[
https://issues.apache.org/jira/browse/CXF-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13944678#comment-13944678
]
Andriy Redko commented on CXF-5576:
-----------------------------------
Hi Sergey,
You are very correct: applications, resources and providers should be coupled
together. However, if there is only one Application available, the resources
and providers could be associated with this application only. I have read it
somewhere and will try to find the direct quote. Because of being more PoC, I
did the simplest thing possible but we can make it much better: I will make use
of getSingletons() and getClasses().
Broadly speaking, we are not getting along well with Application model. F.e.,
getSingletons() method may return resources, providers and features but in
JAXRSServerFactoryBean we have to split them across different methods:
setServiceBeans() and setProviders().
We may come up with several different portable extensions: from simplest ones
to more complex (each built on top on another one). Users can activate them by
need and use as per application demands. What do you think about that?
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)
