Dan Diephouse being hired by Mule has no impact on that. CXF is basically XFire 2.0. Dan D. is one of the leads on CXF with the goal being that CXF is the "new version" of XFire. That is why XFire now recommends CXF. In most cases, it is a "significant upgrade" from XFire 1.2.x. (although there are some features in XFire that are still missing) Dan D. being hired by Mule should not have a negative impact on CXF as part of his job at Mule will be to integrate CXF into Mule.
In anycase, the goal is to replace the xfire stuff in ServiceMix with CXF over time. There are definitely advantages to that. CXF is completely JAX-WS certified. It passes the TCK's. It also passes the JSR181 TCK (xfire does not). The spring configuration/integration in CXF is much better than XFire's. The support for WS-* stuff is better in CXF. Etc..... Dan Kulp [EMAIL PROTECTED] larry hughes wrote: > > I've recently read on the Xfire site that they'd recommend using CXF > instead, probably due to the move of XFire's author to Mule. How does > this affect servicemix? Will the next servicemix depend on CXF instead of > XFire for jsr-181? Just wondering what the upgrade path will look like > for WS down the road. > > Larry > -- View this message in context: http://www.nabble.com/CXF-integration-tf4300789s12049.html#a12314585 Sent from the ServiceMix - User mailing list archive at Nabble.com.
