From announce-return-946-apmail-announce-archive=apache.org@apache.org Mon Oct 11 19:39:34 2010 Return-Path: Delivered-To: apmail-announce-archive@www.apache.org Received: (qmail 11913 invoked from network); 11 Oct 2010 19:39:34 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 11 Oct 2010 19:39:34 -0000 Received: (qmail 60375 invoked by uid 500); 11 Oct 2010 19:39:18 -0000 Delivered-To: apmail-announce-archive@apache.org Received: (qmail 59861 invoked by uid 500); 11 Oct 2010 19:39:17 -0000 Mailing-List: contact announce-help@apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list announce@apache.org Delivered-To: moderator for announce@apache.org Received: (qmail 57021 invoked by uid 99); 11 Oct 2010 19:36:16 -0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on server.dankulp.com X-Spam-Level: X-Msg-File: /tmp/mailfilter-announce@apache.org.Hk7YQOD4qO From: Daniel Kulp To: announce@apache.org, users@cxf.apache.org, dev@cxf.apache.org Subject: [ANNOUNCE] Apache CXF 2.3.0 released! Date: Mon, 11 Oct 2010 15:33:50 -0400 User-Agent: KMail/1.13.5 (Linux/2.6.35; KDE/4.5.2; x86_64; ; ) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1417682.FLOs4yip17"; protocol="application/pgp-signature"; micalg=pgp-sha256 Content-Transfer-Encoding: 7bit Message-Id: <201010111533.56201.dkulp@apache.org> X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No, score=-2.9 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00 shortcircuit=no autolearn=unavailable version=3.3.1 --nextPart1417682.FLOs4yip17 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable The Apache CXF team is proud to announce the availability of the 2.3.0=20 release. Apache CXF is an open source services framework. CXF helps you build and=20 develop services using frontend programming APIs like JAX-WS and JAX-RS.=20 These services can speak a variety of protocols such as SOAP, XML/HTTP,=20 RESTful HTTP, or CORBA and work over a variety of transports such as=20 HTTP, JMS or JBI.=20 CXF includes a broad feature set, but it is primarily focused on the follow= ing=20 areas:=20 =20 * Web Services Standards Support: CXF supports a variety of web service=20 standards including SOAP, the WSI Basic Profile, WSDL, WS-Addressing,=20 WS-Policy, WS-ReliableMessaging, WS-Security, WS-SecurityPolicy, WS-Trust, and WS-SecureConversation.=20 * REST based service creation based on JAX-RS 1.1 standard API's. =20 * Frontends: CXF supports a variety of "frontend" programming models. CXF = =20 provides a JAX-WS 2.2 Compliant frontend. It also includes a "simple=20 frontend" which allows creation of clients and endpoints without annotation= s.=20 CXF supports both contract first development with WSDL and code first=20 development starting from Java. =20 * Ease of use: CXF is designed to be intuitive and easy to use. There are= =20 simple APIs to quickly build code-first services, Maven plug-ins to make=20 tooling integration easy, JAX-WS API support, Spring XML support to make=20 configuration a snap, and much more. What's new in CXF 2.3.0: * JAX-WS 2.2 Compliant (passes TCK) * JAX-RS 1.1 Compliant (passes TCK) * New annotations for Java first use cases to reduce the need for external= =20 configuration and provide more control over the runtime and generated WS= DL * @WSDLDocumentation annotation to add documentation nodes to generated = wsdl * @SchemaValidation annotation to turn on schema validation * @DataBinding to set the databinding used (if other than JAXB) * @GZIP to turn on GZIP compression * @FastInfoset to turn on FastInfoset support * @Logging to turn on and control various Logging functionality * @EndpointProperty to configure endpoint properties * @Policy to associate WS-Policy documents with the service * SOAP/JMS spec implementation. While CXF has supported SOAP over JMS=20 since 2.0, there wasn=E2=80=99t a standard specification to describe how= it=20 should be done so different vendors did things differently and=20 interoperability was impossible. The new SOAP/JMS specification=20 support implements the new SOAP/JMS spec to achieve a higher=20 degree of interoperability. * SDO databinding * Schema Validation support for Aegis Databinding if Woodstox 4 is used=20 for the Stax parser * Many other small tweaks and enhancements, too many to enumerate. See the 2.3 Migration guide at: http://cxf.apache.org/docs/23-migration-guide.html for more details about the release. As always, we welcome feedback on our mailing lists: http://cxf.apache.org/mailing-lists.html Downloads are available from: http://cxf.apache.org/download.html Thanks! The Apache CXF Team=20 http://cxf.apache.org/ --nextPart1417682.FLOs4yip17 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) iQIcBAABCAAGBQJMs2akAAoJEIWPxMT0OFajmPwP/13bqFTle4ODHKeBq/bIsuez 9dRTXcP5pfDeSlLjiwTorcRrq/oVzInxyHZnNQpayCrOK1KKuGnZJKLiVt/nDw0/ 5M0sOvqIEg9zb/YNDbj1MPSD9zS7jsQTLtm+gpEY3sM5eiktia2QV7dfC8wM3zmz 6+vYsSyuahdG1EfX38HntwO633wFx0z2t+DroyaXDDlHzpD9DFklvIYgnnNH8whJ hJf/91URp0F5dNv0M9dzigT1LdP8AbePLZtPKTysWPlhhTma9B7i+smgKtuT/7TL UsVbhVypUa8gkVI0K+hxHnY0TcyRFJE3Uwe20xYWBrXDhmnc4H8z6gmstXexCNHd ZsmwSt1d5e+vvic3m5cOH4YU8GEMNzQs01dT1lnRxsA6ZsDofRZ/4GD/x5Ly4KZA t9FrD4Qsrm27X5I+2Yylyqyggg/pU3edoOSjhAVGPc6bPWtr4NLyIdjR2Ry1a1o7 9JfFLKKzxpPem2h36tfL6pnSeJ6y1/ycd502JY3NBnsz1mnNKfoW/YVOTS2PnpmV 7LnPgfq5m1Owcpdj0W6+QN1Yc2h+m50yG9c8d7gDYFYLAaoIXfKSHQLG0ZhIk+1B eaSGSwYY6KprYzgFvF+z7OZduexQIcBzQf2TYyrRwxqNWIBFNKiAvdNWR7hloWjY 0XPiB2KvXz2OI9NUfnN7 =m6kV -----END PGP SIGNATURE----- --nextPart1417682.FLOs4yip17--