We are using CXF to build an SSO and general intergration platform at my workplace.
We initially started out with XFire but decided in the last minute (and about three days after CXF 2.0 was released IIRC) to go with CXF instead, even though it meant scraping some of work we already had done on some general components. We did this even though XFire is very mature and production ready, because if you want to build software with a future, it's best to use technologies that have a future as well; CXF is young and has its kinks, but it also has momentum and a growing community as far as I can tell, and this made it a better option for us then XFire. I personally consider CXF production ready; we haven't got any CXF services in production systems just yet, though we have some handfuls in staging environments and they are humming along quite handsomly. 2007/10/23, Greg Thoenen <[EMAIL PROTECTED]>: > Hi, all. > > I'm currently evaluating web service frameworks that might provide our > web services on the server side. CXF is a top contender, but I'm a > little confused about its maturity. It is still in the Apache > incubator, however it has releases that appear to me to be "production" > releases (e.g. 2.0.1, as opposed to 2.0-MC1 or 2.0-RC1, etc.). > > This leads me to some (related) questions: Is CXF considered production > ready? If so, is anyone using it in production systems, and what are > people's experiences regarding its production readiness? > > An unrelated question that may be pretty ignorant (sorry) is why Apache > is sponsoring CXF rather than modifying the web service framework > (Axis2) that it already is invested in? Was it deemed that it would > take more effort to modify Axis2 to support JAX-WS, etc., as to start > with XFire and do it? > > Thanks in advance, > Greg > > -- Venlig hilsen / Kind regards, Christian Vest Hansen.
