CXF 2.0.2 发布了

经过快一个月的投票，CXF2.0.2 终于发布了。
下面是从CXF 邮件列表上转来的消息。

The Apache Incubator CXF team is proud to announce the availability of
the 2.0.2 release!

Apache CXF is an open source services framework. CXF helps you build
and develop services using frontend programming APIs, like JAX-WS. These
services can speak a variety of protocols such as SOAP, XML/HTTP,
RESTful HTTP, or CORBA and work over a variety of transports such as
HTTP, JMS or JBI.


CXF includes a broad feature set, but it is primarily focused on the
following areas:

* Web Services Standards Support: CXF supports a variety of web service
standards including SOAP, the Basic Profile, WSDL, WS-Addressing,
WS-Policy, WS-ReliableMessaging, and WS-Security.

* Frontends: CXF supports a variety of "frontend" programming models. CXF   
provides a JAX-WS Compliant frontend. It also includes a "simple
frontend" which allows creation of clients and endpoints without   
annotations. CXF supports both contract first development with WSDL and   
code first development starting from Java.

* Ease of use: CXF is designed to be intuitive and easy to use. There   
are simple APIs to quickly build code-first services, Maven plug-ins to   
make tooling integration easy, JAX-WS API support, Spring 2.0 XML
support to make configuration a snap, and much more.


This release contains the following improvements:
  * Configuration support for the WS-Policy engine
  * WS-Addressing Feature (easier to configure WS-A)
  * WS-Reliable Messaging Feature (easier to configure WS-RM)
  * Lots of sample improvements
  * Several Spring configuration improvements
  * Over 70 other bug fixes and enhancements

For more information see:
 * Download: http://incubator.apache.org/cxf/download.html
 * Website: http://incubator.apache.org/cxf/
 * Release Notes:
http://incubator.apache.org/cxf/apache-cxf-202-incubating-release-notes.html
 * Mailing lists: http://incubator.apache.org/cxf/mailing-lists.html


If you have feedback, questions or would like to get involved in the CXF
project please join the mailing lists and let us know your thoughts.

The Apache Incubator CXF Team
http://incubator.apache.org/cxf/

呵呵，以前lz不是发过一个么？
这个跟那个是一样的么？

看来LZ是CXF的忠实fans，可以说说你的应用经验呀。

以前发的是2.0.1的发布消息, 这次是2.0.2发布的消息.
2.0.2主要是修正了2.0.1版本中的很多个bug,建议大家升级到2.0.2.

我是CXF的Committer,应用谈不上就是对CXF代码有所了解,所以就在这做广告了.
还有大家在使用CXF过程遇到的问题可以直接发到
http://groups.google.com/group/cxf-zh
可以获得有个CXF使用的中文支持.

上次lz不是在group里发过一个“CXF2.0.2 抢鲜试用”么？
当时我就从那个地址下载了，:)
那个跟这个是同样的么？同样的话我就不再下了，呵呵。

jnn是CXF的Committer啊！
景仰ing！

对了，麻烦帮忙看看我那个“[SOA] 如何让CXF导出重载的方法”的帖子。
那算是CXF的bug么？
以前XFire在Wrapped方式的时候是可以自动重命名重载(overload)方法的。

这次是正式版, 与上次哪个版本相比修正了更多的Bug.

看了你的帖子, 我不太清楚XFire提供的自动命名机制是什么样的.
但是对于Wrapped的Document/Literal来说由于传递的消息element名字和wsdl:operation的名字是一样的,这就决定来同名函数(不同参数的)在影射到具体wsdl:operation的过程中存在二义性.

查了一下JAXWS 2.0的规范在 3.6.2.1 中有这么一句

Conformance (Default wrapper bean names): In the absence of customizations, the wrapper request bean class MUST be named the same as the method and the wrapper response bean class MUST be named the same as the method with a “Response” suffix. The first letter of each bean name is capitalized to follow Java class naming conventions.

从规范的角度上来说,(在没有客户化的情况下,我的理解是没有通过annotation进行设置方法名) CXF扔出异常应该不算是个bug.

呵呵，XFire在wrapped方式下，如果3个a()，它会自动命名为a()、a1()、a2()。
相当的方便，呵呵。

但是这种命名方式的意义不大，客户端调用的时候，还需要通过数字后缀来窥探参数个数？