Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <7b774c950708071027v472a2ee2y13c7b50de8312878@mail.gmail.com>
Date: Tue, 7 Aug 2007 13:27:01 -0400
From: "Dan Diephouse" <dan@envoisolutions.com>
To: cxf-dev@incubator.apache.org, dkulp@apache.org
Subject: Re: 2.1 thoughts......
In-Reply-To: <200708071213.34356.dkulp@apache.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_159133_30704104.1186507621954"
References: <200708071213.34356.dkulp@apache.org>

------=_Part_159133_30704104.1186507621954
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 8/7/07, Daniel Kulp <dkulp@apache.org> wrote:

> 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.


The runtime support is relatively trivial to port from XFire. The part that
concerns me more is the tooling as I'm not familiar with the tooling APIs at
all :-)

>
> 4) Rest stuff - all the buzzword compatible stuff.   :-)


JSR 311 support would be nice, but quite a bit of work.

5) WS-* specs - do we have time to tackle any more of these at this
> point?   Which ones should we prioritize?


The big ones that I see are: WS-SecureConversation, WS-Trust and
WS-SecurityPolicy. They're a bit of work though. I've started some work
locally on these, but haven't gotten that for - I'm more stuck in the joys
of getting JAXB and WS-SecurityPolicy to play well with our existing
generated classes for WS-Policy.

>
>
> 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.   :-)
>
>
As I've hinted at before I think JAX-WS support should be our feature
whereby we determine when we release. I.e. once we pass the TCK, lets do a
release. If other features aren't done, we can knock off future releases
quickly as those features are completed. We might even make it out of the
incubator by then, so it'd be much faster :-) If we keep to the frequent
release schedule, this should help us get out bug fixes faster and generate
more project publicity as well.

- Dan


-- 
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog

------=_Part_159133_30704104.1186507621954--