[
https://issues.apache.org/jira/browse/CXF-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13918641#comment-13918641
]
Sergey Beryozkin commented on CXF-5576:
---------------------------------------
Hi Andriy, All,
To me it looks like it is nearly complete. It's quite impressive really.
By the way, it reminds me a bit about the way Spring annotation-driven
configuration works.
Effectively we have 2 resources, the extension and the servlet, this is all,
and it works.
The scope for the re-use between JAX-RS and JAX-WS is close to zero, but the
good thing it is effectively a copy and paste and renaming of few annotations
and some code references for JAX-WS + CDI to work too.
I guess we are talking here about either a single new module,
rt/integration/cdi, with optional JAX-WS & JAX-RS deps and 4 (8) source files
in total...Or, if that is not clean or we have a scope for big
frontend-specific CDI code branches, then 2 modules, one per JAX-RS and one per
JAX-WS ?
To be honest I kind of prefer the single module as we may start duplicating
common bits and pieces if we go the separate module rules...If we have a single
module then JAX-RS endpoints will simply add a JAX-RS dep, same for JAX-WS...
Thoughts ?
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
> 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)
