cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergey Beryozkin <>
Subject Re: Follow-up on CDI integration
Date Wed, 19 Feb 2014 22:14:44 GMT
On 19/02/14 20:42, Christian Schneider wrote:
>  From my side the main point is that we should NOT start to reinvent the
> wheel and create our own small CDI impl.
No worries, we've agreed to it.

> I think if we start with a CDI container or Java EE server and implement
> CXF support as a portable CDI extension we will have full
> support of all CDI features while not getting into the way of the
> container.

All I'm looking for is for users be able to utilize CDI with the help of 
Weld/Delta Spike while working in the standalone/servlet containers such 
as Tomcat and Jetty, without getting into the way of the containers 
already doing CDI 'natively'.

AFAIK I'm not looking for the full CDI support at the JAX-RS end, having 
a basic injection supported will do my 'day' for a start for sure :-), 
the rest - up to yourself, Andriy and others

> So for example we would not scan for the @Path annotation ourself and
> instead tell the CDI container we want to be called back if it hits a
> @Path annotation. Not sure how to do this exactly but I am pretty sure
> CDI extensions can do that.
The auto-discovery is the next/orthogonal issue, I'm not concerned about 
it as far as the JAX-RS CDI integration is concerned...

Cheers, Sergey

> Christian
> Am 19.02.2014 12:36, schrieb Sergey Beryozkin:
>> Hi Andriy
>> On 18/02/14 22:44, Andrey Redko wrote:
>>> Hey guys,
>>> Follow-up on a recent conversation, I am wondering if someone is looking
>>> into PoC for CDI integration in CXF? (Christian?) I would like to spend
>>> some time and try to come up with easy way to have basic CDI support in
>>>   JAX-RS / JAX-WS services. Please let me know if someone is already
>>> working on that so I will work on something else.
>> AFAIK I'm interested in seeing the basic injection of beans working in
>> standalone containers like Tomcat as per the JAXRS 2.0 spec describing
>> the optional integration with CDI, for example,
>> @Path("/")
>> public class MyRoot {
>>   @Inject Book book;
>>   @GET
>>   public Book getBook() {
>>       return book;
>>   }
>> }
>> IMHO the same should work for JAXWS services. And it should be enabled
>> optionally, so as not to interfere with EE containers doing their own
>> CDI work.
>> Christian, is it in line with what you'd like to happen when
>> integrating JAX-WS endpoints with CDI ?
>> Andrei, may be you can play a bit with the JAX-RS 2.0 level CDI
>> integration and then ask Christian review it and may be agree on the
>> common approach toward enabling the basic injection support for the
>> frontends ?

Sergey Beryozkin

Talend Community Coders


View raw message