On Monday 25 October 2010 7:53:46 pm Robert Liguori wrote: > Just FYI... > > Considering the overview of of Apache CXF 2.3.0 > (http://cxf.apache.org/apache-cxf-230-release-notes.html), I really think > that this build should have been 3.0.0, but that's just my opinion. I > believe a lot of the support libraries were also updated. Here's the text > from the web page describing the updates: >
Technically, if that's the benchmark, 2.3 should have been 5.0. 2.0 -> 2.1 was a MUCH bigger (from a user impact standpoint) than any other release of CXF. Updating from JAX-WS 2.0 to 2.1 was huge, required all new generated code, broke a bunch of things, etc... 2.2 added JAX-RS compliant frontend, WS-Security Policy/WS-Conversation/WS-Trust support, and a fairly new/improved Aegis type system. Thus, by your benchmark 2.1 should have been 3.0 2.2 should have been 4.0 2.3 should have been 5.0 Seriously, we've kind of been thinking that the major version number is dictated more by achitectural structure (XFire -> CXF type thing) that would require large amount of user visible changes. The minor version is more the major features, but existing code should migrate with small amount of effort. With that definition, it's 2.3. :-) Dan > "Apache CXF 2.3.0 is a pretty significant upgrade from the 2.2.x series of > releases. There are plenty of new features and other improvements > including: > > a.. JAX-WS 2.2 Support > b.. JAX-RS 1.1 Support > c.. New annotations of java first use cases > a.. @WSDLDocumentation annotation to add documentation nodes to > generated wsdl b.. @SchemaValidation annotation to turn on schema > validation > c.. @DataBinding to set the databinding used (if other than JAXB) > d.. @GZIP to turn on GZIP compression > e.. @FastInfoset to turn on FastInfoset support > f.. @Logging to turn on and control various Logging functionality > g.. @EndpointProperty to configure endpoint properties > h.. @Policy to associate WS-Policy documents with the service > d.. SOAP/JMS spec implementation > e.. SDO databinding > f.. Schema Validation support for Aegis Databinding if Woodstox 4 is used > for the Stax parser" Anyone agree? -- Daniel Kulp [email protected] http://dankulp.com/blog
