Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 89A7D118D9 for ; Thu, 27 Mar 2014 11:38:36 +0000 (UTC) Received: (qmail 5062 invoked by uid 500); 27 Mar 2014 11:38:35 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 5012 invoked by uid 500); 27 Mar 2014 11:38:33 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 4844 invoked by uid 99); 27 Mar 2014 11:38:29 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Mar 2014 11:38:29 +0000 Date: Thu, 27 Mar 2014 11:38:28 +0000 (UTC) From: "Andriy Redko (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (CXF-5576) Initital support for CDI integration MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CXF-5576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949186#comment-13949186 ] Andriy Redko edited comment on CXF-5576 at 3/27/14 11:38 AM: ------------------------------------------------------------- Hi Sergey, Gotcha ... The beans without @Inject won't be wired up but it may be worked around mostly all the time with @Produces and setting the properties manually. Exploiting Application more (its properties, classes and singletons) is giving as mostly everything to configure the application properly, I am very close to have it implemented (will try to finish up this week, add test cases, examples). The one "hack" we have to absorb is about Feature: JAX-RS spec defines Feature interface and we also have one. We may support only ours as it allows us to customize JAXRSServerFactoryBean with probably all we need. Sounds right? Thanks. Andriy. was (Author: reta): Hi Sergey, Gotcha ... The beans without @Inject won't be wired up but it may be worked around mostly all the time with @Produces and setting the properties manually. Exploiting Application more (its properties, classes and singletons) is giving as mostly everything to configure the application properly, I am very close to have it implemented (will try to finish up this week, add test cases, tests). The one "hack" we have to absorb is about Feature: JAX-RS spec defines Feature interface and we also have one. We may support only ours as it allows us to customize JAXRSServerFactoryBean with probably all we need. Sounds right? Thanks. Andriy. > 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)