On 7/25/07, Christopher Moesel <[EMAIL PROTECTED]> wrote:
I thought the article was good, but it seemed like the author kept using "XFire" and "CXF" interchangeably. It could be confusing for those who are not familiar with both frameworks-- some questions that *say* XFire really *mean* CXF. Although CXF can be considered "XFire 2.0", it would have been nice to see the CXF branding consistent throughout the article.
One of the take-aways from the booth was that the confusion is very real for most folks. People are familiar with the XFire name, and the usual suspects for SOAP frameworks that people experiment with are still XFire, AXIS, and then maybe a commercial offering like whoever owns Systinet at this point. We need to make a real effort to educate people on the existence of CXF, what it does, and how it relates to other packages. If you Google "java soap framework", CXF appears (in the form of an incubating status page) part way down, but otherwise it's still all XFire and AXIS. My suggestions in this regard: 1) Graduate. Incubation only makes sense to people who understand the inner workings of Apache. 2) The various commercial entities who participate in CXF development should issue press releases about the graduation when it happens. Showing up in the first 5 Google results for "java soap framework" should be a project goal. My $0.02. -- Paul
