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 Thu, 27 Mar 2014 12:16:22 GMT


Sergey Beryozkin commented on CXF-5576:

Hi Andriy

I'm a bit confused now. As I said, IMHO, if we do the customizations from the code then I
honestly do not see the value of using our CDI extension. In case of JAX-RS people can just
write Application and then use CXFNonSpringJaxrsServlet and be done; they use this approach
when they do not want to depend on the injection technology, so why mix in CDI in this process.

Personally I'd be interested for a start to see how application-specific properties can be
injected into BookStore. This approach

seems nice to me, why can't we use it in the tests ? Lets chat about JAXRSServerFactoryBean
customizations later, lets explore first how the properties can be injected into BookStore
for a start...

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