cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CXF-5576) Initital support for CDI integration
Date Wed, 26 Mar 2014 16:01:15 GMT

    [ https://issues.apache.org/jira/browse/CXF-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13948028#comment-13948028
] 

Sergey Beryozkin edited comment on CXF-5576 at 3/26/14 3:59 PM:
----------------------------------------------------------------

Hi Andriy

I just don't see a point in doing CDI with our extensions if we can't provide the injection
support for the primitive values, The Zero configuration approach is all right for basic cases,
but I can't imagine users doing a lot of the actual work with the CXF CDI module otherwise.
For example, In 80-90% cases, JAX-RS JSONProvider needs to have some of its properties set,
but what is the added value of CDI if to get this rather regular task done the users would
have to set the properties from the code ? Of course, in TomEE+ or JBoss, etc, they'd get
a better support (I presume).

Personally I'd vote for keeping the Zero based approach for now and see if we can figure out
how to support the declarative injection of basic properties the CDI way...
How about though updating the test to have BookStore injected some text property and validating
on the client the value has been injected :-) ?


Thanks, Sergey




was (Author: sergey_beryozkin):
Hi Andriy

I just don't see a point in doing CDI with our extensions if we can't provide the injection
support for the primitive values, The Zero configuration approach is all right for basic cases,
but I can't imagine users doing a lot of actual work with the CXF CDI module otherwise. For
example, In 80-90% cases, JAX-RS JSONProvider needs to have some of its properties set, but
what it the added value of the CDI if to get this rather regular task done the users would
have to set the properties from the code ? Of course, in TomEE+ or JBoss, etc, they'd get
a better support (I presume).

Personally I'd vote for keeping the Zero based approach for now and see if we can figure out
how to support the declarative injection of basic properties the CDI way...
How about though updating the test to have BookStore injected some text property and validating
on the client the value has been injected :-) ?


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)

Mime
View raw message