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 B7594CBA0 for ; Thu, 4 Jul 2013 08:52:11 +0000 (UTC) Received: (qmail 28952 invoked by uid 500); 4 Jul 2013 08:52:09 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 28717 invoked by uid 500); 4 Jul 2013 08:52:09 -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 28558 invoked by uid 99); 4 Jul 2013 08:52:06 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Jul 2013 08:52:06 +0000 Received: from localhost (HELO mail-wg0-f43.google.com) (127.0.0.1) (smtp-auth username coheigea, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Jul 2013 08:52:06 +0000 Received: by mail-wg0-f43.google.com with SMTP id z11so884677wgg.34 for ; Thu, 04 Jul 2013 01:52:04 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=GAr4BHRL4Tcd6RA8KAUXXe7wlk3imv7lRU9DEDewN8o=; b=ZrRMi2v3pF/dx6mr5FHvyofVFqMg541h8xilJZiSrttuy0ViCaap8wfrtgQlSW+26i xOvh0EWQLDHlnJb95MYyln3LF4FpQMfPM96Nb2T1IcMHjdqziHEj5sVE5P/+X4m6fiLk y8yBaOWhZEW/KxI60QpHGtDLalYviZ8ZEGWaWpd36dkksTEDkb+1qrPzJ3WAN1O80fg7 WfyUfbtagRjuD/wVlCX4CxM/csLC5ZKajj2kSiVS4xP6m0oVMAGl5VOVoX5ZgoUclil+ fM80O1AhhiNotdmU2r6a3M3wNS+G5kW66DB7HACWNbaW+xu1CHX62Nrkx0cvEJ4rm791 h55A== MIME-Version: 1.0 X-Received: by 10.180.91.107 with SMTP id cd11mr2784560wib.12.1372927924394; Thu, 04 Jul 2013 01:52:04 -0700 (PDT) Reply-To: coheigea@apache.org Received: by 10.194.121.4 with HTTP; Thu, 4 Jul 2013 01:52:04 -0700 (PDT) In-Reply-To: <51D4D5CC.1020506@sosnoski.com> References: <5740A22B-10EB-46CC-BC46-1FF8558B2F81@apache.org> <51D4D5CC.1020506@sosnoski.com> Date: Thu, 4 Jul 2013 10:52:04 +0200 Message-ID: Subject: Re: [DISCUSS] api+rt-core -> core From: Colm O hEigeartaigh To: "dev@cxf.apache.org" Content-Type: multipart/alternative; boundary=f46d043bdf743c66f104e0abb1cd --f46d043bdf743c66f104e0abb1cd Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable +1. Colm. On Thu, Jul 4, 2013 at 3:54 AM, Dennis Sosnoski wrote: > +1 > > - Dennis > > > On 07/04/2013 06:39 AM, Daniel Kulp wrote: > >> For 3.0, I'd like to combine both cxf-api and cxf-rt-core into a single >> jar/bundle. I'd likely just call it cxf-core, but I'm open to other >> suggestions (cxf-kernel?). >> >> We originally tried to have a separate jar for "api" to make javadoc >> generation easier, but it pretty much doesn't work. Many of the classe= s >> (like the Service Factories and client factories and JAX-RS client thing= s >> and much much more) that you really would need are not part of api and t= hus >> don't appear in the "api" javadoc anyway. Thus, that reason is pointle= ss >> and not working. >> >> API is also WAY WAY more than just "API" now. There are interceptors, >> data binding things, all kinds of concrete utility things, etc=85 API = is >> about 1MB whereas "core" is about 270K. Kind of shows where the real >> "core" stuff is. >> >> As it is, right now, you cannot really have api without rt-core anyway. >> By combining them, we can get rid of some of the dynamic import things = and >> such in OSGi (to find the Bus factory). One less jar to deal with as >> well. The jaxrs basic sample would be down to cxf-core, >> cxf-transports-http, cxf-rt-frontend-jaxrs, and the related 3rd party de= ps. >> >> Thoughts? >> >> > --=20 Colm O hEigeartaigh Talend Community Coder http://coders.talend.com --f46d043bdf743c66f104e0abb1cd--