[
https://issues.apache.org/jira/browse/CXF-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949336#comment-13949336
]
Sergey Beryozkin commented on CXF-5576:
---------------------------------------
Hi Andriy,
sounds good :-), and please take your time, IMHO it is not very urgent. if we
can have just a zero based approach covered before 3.0 then it would be nice.
I'm still a bit unclear about having JAX-RS and JAX-WS extensions collocated.
Assuming we do go ahead with the single module only then I guess it both JAX-RS
and later JAX-WS dependencies would need to be made optional. Another question
is whether it is OK for a single javax.enterprise.inject.spi.Extension resource
list both JAX-RS and JAX-WS extensions (this will need to be done if we go
ahead with a single module). It is probably OK because I guess we can expect
that the user will deploy either JAX-WS or JAX-RS... I guess we need to sort
out these issues before actually resolving this JIRA
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)
