cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] [Commented] (CXF-5576) Initital support for CDI integration
Date Sun, 16 Mar 2014 19:56:42 GMT


Sergey Beryozkin commented on CXF-5576:


perhaps multiple CDI instantiation strategies can be supported which can be a good compromise.

The current approach looks very neat/clean to me for a pure WAR or embedded HTTP container
approach. We can have something else done for OSGI case where the default/shared servlet path
may be reasonable, but I'm happy to keep the current approach supported too, it won't interfere
with the other styles of managing CDI-aware endpoints :-). 
I think the current approach and the one you propose can co-exist, example, we have a default
CXF OSGI HTTP transport and CXFBluepringServlet - different non-intersecting mechanisms 

Andrey, just a quick question,  can have abstract CdiResourceExtension introduced, JAXRSCdiResourceExtension
extending it, and CXFCDIServlet working with CdiResourceExtension only ? This and the possible
interface will make it portable

Thanks, Sergey  

> Initital support for CDI integration
> ------------------------------------
>                 Key: CXF-5576
>                 URL:
>             Project: CXF
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 3.0.0
>            Reporter: Andriy Redko
>            Assignee: Andriy Redko
>              Labels: cdi
>         Attachments:,
> 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

View raw message