Return-Path: X-Original-To: apmail-cxf-dev-archive@www.apache.org Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D8B551788C for ; Thu, 9 Oct 2014 11:38:01 +0000 (UTC) Received: (qmail 24295 invoked by uid 500); 9 Oct 2014 11:37:59 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 24164 invoked by uid 500); 9 Oct 2014 11:37:59 -0000 Mailing-List: contact dev-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 dev@cxf.apache.org Received: (qmail 24140 invoked by uid 99); 9 Oct 2014 11:37:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Oct 2014 11:37:59 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sberyozkin@gmail.com designates 74.125.82.44 as permitted sender) Received: from [74.125.82.44] (HELO mail-wg0-f44.google.com) (74.125.82.44) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Oct 2014 11:37:52 +0000 Received: by mail-wg0-f44.google.com with SMTP id y10so1028835wgg.15 for ; Thu, 09 Oct 2014 04:37:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=6slD+S30o9fZOVSU5yr6BULVjUZYI4wTon6VzETBly0=; b=sadEQFLqWXoB3yiLaAikDvOdVtaPH0NaZX8k6xf0kxAgEokAudYIApRBvHtqeAzfJ/ NtFuxqh+WeDU9k2WbCTpfucfgwyXTPD2Aw6F5iQKSznfpmY8Oc9NHirY2Y22BEI9egXR oV4sTbWTtfe726sFAMMIUphIuozlbyfA+h2fLT+3oPwqTu0nyJL6Y6cEILja/8jm2kwj zgIp/56FCNqNRXouxDaNXSD8qFgCfplI9msIhZ9G+bACTP7QMTlO1tJ8G1l49v7hMEfC 2xyt8/a0bJn1Ip6oNg5ma7CsK0FyzQejuVqUwQlHNa2bTg9bPGY5P4FxPXzlrKD8d9pE CxWw== X-Received: by 10.194.58.50 with SMTP id n18mr17008919wjq.47.1412854650862; Thu, 09 Oct 2014 04:37:30 -0700 (PDT) Received: from [192.168.2.7] ([109.255.231.6]) by mx.google.com with ESMTPSA id gw6sm5286884wib.8.2014.10.09.04.37.29 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 Oct 2014 04:37:30 -0700 (PDT) Message-ID: <54367379.5010109@gmail.com> Date: Thu, 09 Oct 2014 12:37:29 +0100 From: Sergey Beryozkin User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2 MIME-Version: 1.0 To: dev@cxf.apache.org, users Subject: Re: EJB integration for JAX-RS2.0 in CXF References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi On 09/10/14 10:06, Bin Zhu wrote: > Hi, > Does current CXF support EJB based JAX-RS 2.0 application? If yes, is there > requirement for EJB container? any additional configuration needed for > application server? Thanks. > > > Spec for EJB support: > > In a product that supports EJBs, an implementation MUST support the use of > stateless and singleton session > beans as root resource classes, providers and Application subclasses. > No, CXF does not have its own EJB integration project in place yet. CDI - yes, Andriy Redko did it. TomEE has it AFAIK. There was a GSOC project few years back dedicated to it but it was not completed. Might be worth having a light-weight CXF JAX-RS 2.0 EJB integration project as well, that would have CXF offering a complete integration support... Cheers, Sergey