Hi Andrei
On 27/03/13 18:24, Andrei Shakirin wrote:
+1 for skipping 2.8 and releasing 3.0 end of this year.
@Sergei: let us to discuss how I could help with 2.0 TCK.
I'm trying to get the server part close enough to be tested against TCK.
There are 3 issues which I'm aware at the moment that need to be completed:
1. support for server-side media type quality parameters (;qs), this is
needed
2. support fro injection of Configuration context - should be
straightforward enough
3. bean validation support - the latter is important but has just been
confirmed to be an optional feature - that said I think we can probably
get it done for RS but also for WS
I think only 1 is required at this stage to start working with TCK, plus
minor bits and pieces to be fixed to get (server-part) TCK passed :-).
The TCK we have is not final but should be close enough to the final
one. The client implementations tests will be done later in the year
I'll get back to you once I do an initial run later on
Thanks Sergey
Regards,
Andrei.
-----Original Message-----
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Montag, 25. März 2013 19:19
To: dev@cxf.apache.org
Subject: Thoughts about a 2.8 release (or not)…
We're getting close to April which normally would be the next release (2.8).
However, looking things over, I'm not sure it makes sense at this time.
Looking at trunk, the only major change (which is admittedly a big one), is
updating the JAX-RS 2.0 stuff from m10 to the RC level. However, it's not
complete yet. Almost everything else has been back ported to 2.7.x. The
other major chunk of work that is happening is on the wss4j2 branch, but
that isn't ready for for release yet either. (and has some backwards compat
issues to resolve if it would go on a 2.x line)
According to the agreements Apache has with Oracle, we really cannot
"release" code that doesn't pass the TCK (which the 2.0 works would not).
Technically, we should not have released 2.7.0 as a release. We can release
things like "tech previews" or "beta" or similar, but not a full release.
Since
we are working on trying to renew the agreements, Oracle is paying
attention to us pretty closely right now.
So, what am I getting at? In order to release 2.8 in a few weeks, we'd either
need to back out all the JAX-RS 2.0 stuff to 1.1 level OR everyone jump in full
force and get it to pass the TCK. I really don't see either happening.
Backing
out to 1.1 would be silly and the 2.0 TCK stuff is a ton of work. Thus, my
suggestion would be to skip a big release this April and concentrate on bigger
things for our Oct/Nov release. Possibly make that a CXF 3.0 release instead
of 2.8 where we can clean up some stuff, break a few things (like change the
couple API's that currently force WSDL4J on JAX-RS users), etc… We can
incorporate the WSS4J2 changes as part of this as well. If we go this route,
we could likely start a series of "beta" releases or similar in June or so to
get
people looking at it and testing with it.
Any thoughts?
--
Daniel Kulp
dk...@apache.org - http://dankulp.com/blog Talend Community Coder -
http://coders.talend.com
