Yeah...

I definitely think it should be 2.3.0/3.0.0

Kinda like what WSDL did with 1.2/2.0.

:)


--------------------------------------------------
From: "Johan Edstrom" <[email protected]>
Sent: Monday, October 25, 2010 8:21 PM
To: <[email protected]>
Subject: Re: 2.3.0 probably shoud've been 3.0.0

I think 2.3.0 also encompasses more changes in the API, i.e you need a little bit of a transition guide.

On Oct 25, 2010, at 5:53 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:

"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?

Johan Edstrom

[email protected]

They that can give up essential liberty to purchase a little temporary safety, deserve neither liberty nor safety.

Benjamin Franklin, Historical Review of Pennsylvania, 1759






Reply via email to