[
https://issues.apache.org/jira/browse/CXF-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910177#comment-13910177
]
Sergey Beryozkin commented on CXF-5576:
---------------------------------------
Contexts are actually thread-safe proxies so they would be as good the matches
for CDI as they are for other frameworks; the reason the JAX-RS 2.0 does not
recommend using @Inject to inject the contexts is to minimize the loss of
portability.
" I think what should work is to get the fully injected (from standard CDI
point of view) bean from the CDI container and use it in jaxrs. So anything
that is not covered by CDI woud work as before."
Yes, that is right. I guess the same would be the case for JAX-WS, hence I'm
trying not to get this effort being all about JAX-RS really; but I'm OK with
you doing something else for JAX-WS, you've already started a git project, so
I'll support whatever you do on the JAX-WS end...
Cheers, 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
>
> 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.1.5#6160)
