Return-Path: Delivered-To: apmail-incubator-cxf-dev-archive@locus.apache.org Received: (qmail 1599 invoked from network); 7 Aug 2007 16:14:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Aug 2007 16:14:05 -0000 Received: (qmail 49419 invoked by uid 500); 7 Aug 2007 16:14:04 -0000 Delivered-To: apmail-incubator-cxf-dev-archive@incubator.apache.org Received: (qmail 49359 invoked by uid 500); 7 Aug 2007 16:14:04 -0000 Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cxf-dev@incubator.apache.org Delivered-To: mailing list cxf-dev@incubator.apache.org Received: (qmail 49350 invoked by uid 99); 7 Aug 2007 16:14:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Aug 2007 09:14:04 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_HELO_PASS,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [64.79.194.121] (HELO mesa2.com) (64.79.194.121) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Aug 2007 16:13:56 +0000 Received: from [63.65.132.8] (account jdkulp HELO dilbert.boston.amer.iona.com) by mesa2.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 1165015 for cxf-dev@incubator.apache.org; Tue, 07 Aug 2007 12:13:34 -0400 From: Daniel Kulp Reply-To: dkulp@apache.org To: cxf-dev@incubator.apache.org Subject: 2.1 thoughts...... Date: Tue, 7 Aug 2007 12:13:34 -0400 User-Agent: KMail/1.9.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200708071213.34356.dkulp@apache.org> X-Virus-Checked: Checked by ClamAV on apache.org With 2.0.1 almost out the door (getting votes when everyone is on vacation sucks), I'd like to take a minute to think about what should go into 2.1. We've tossed around a bunch of ideas and I'd like to get them written down. I'll probably start a "wish list" wiki page once the ideas get flowing, but for now, here's my list of stuff I've seen floating around: 1) JAX-WS 2.1/JAXB 2.1 - this is a fairly large amount of work as there are some very significant changes that will involve code generation changes, java -> wsdl changes, runtime support changes, etc.... 2) Data bindings - XmlBeans and JIBX have been on the list for a while and I'm sure more XFire folks could find CXF more useful if we got those working. There are two parts: runtime and tooling. 3) JavaScript stuff - the javascript frontend needs some refactoring to allow calling other services with it, make it not dependent on the jaxws frontend, etc.... Also the js donation from Basis Tech would be great to get wired in. (if we can get the grant set, too many people on vacation) 4) Rest stuff - all the buzzword compatible stuff. :-) 5) WS-* specs - do we have time to tackle any more of these at this point? Which ones should we prioritize? 6) OSGI bundling - I think adding simple OSGI manifests for our jars would be fairly easy. However, should we create some "bundles" to represent common functionality? (like JAX-WS/SOAP/HTTP bundle) I hate to ask for more ideas as that alone is a TON of work, but at this point, let's get the ideas flowing. :-) -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 daniel.kulp@iona.com http://www.dankulp.com/blog