[
https://issues.apache.org/jira/browse/CXF-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949226#comment-13949226
]
Sergey Beryozkin commented on CXF-5576:
---------------------------------------
Hi Andriy, just would like to clarify what IMHO makes sense investigating:
We have many CXF interceptors (and JAX-RS providers) which won't be have
@Inject added to their fields/setters. In fact we probably can assert they
won't have @Named added to them. And JAX-WS has no Application. So IMHO doing
the initial investigation of the various options at the BookStore level first
can give an idea what is realistically possible with respect to bringing the
existing beans into the CDI space...Once we know about all the options we can
decide what to do about server beans customizations.
IMHO, the CDI module would have to ship ManagedJaxrsServerFactoryBean with
@Named (similarly for JAXWS) so that its properties can be externally managed.
But I'd like to explore first how this can be done with the application bean
like BookStore
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)
