Axis vs XFire

Http://swik.net/Axis-vs-XFire

Axis and XFire are competing Java Web service frameworks; Axis is an Apache project and XFire are a Codehaus project.

It is difficult to compare the Axis and XFire Web services frameworks for the purpose of the deciding which one to adopt. Both Web Services frameworks has some significant challenges associated with using them, and there is good reasons to Ch Oose either one or the other. It all depends on where the emphasis was being placed when comparing them:stability, performance, or ease of use. 2 Branches of Axis

Before comparing axis to anything else, however, it's important to make note of the a fact that there be both separate Axis Frameworks:axis 1 and Axis2. The Axis development team have shifted to AXIS2 and have made it clear that while Axis1 bugs could be fixed, all enhancement a ND feature work are going to take place in Axis2, which is a ground-up reimplementation of the framework using a very Diffe Rent model.

Axis1 is a stable platform-stable to the point of ossification. It does has outstanding bugs, but there seems to being little effort on the part of the developers to correct them, or even Evaluate patches contributed by non-axis developers. Recent months has seen a drop-off even in responses to Axis1 question on the Axis-users mailing list.

For this reason, it's reasonable to continue to use AXIS1 for legacy applications that's already working and do not Require major changes, as its very stability are an advantage there. However, in developing new applications It's probably advisable to look to Axis2, since it's under active development an D It has a large, active community associated with it. Therefore it makes to compare Axis2 and XFire for purposes of selecting a platform for new applications, or Por Ting an existing legacy application to one of the current frameworks. comparing Axis2 and XFire

With the differentiates Axis2 and XFire? Perhaps before highlighting differences we should look at the ways in which they is the Same:both has active user and D Eveloper communities as of February, both has an almost identical number of open bugs as of February, B Oth a almost identical quantity and distribution of blocker, Critical, Major, Minor and Trivial bugs in their jiras (Axis2 JIRA, XFire JIRA)

So from this we can conclude the terms of the number of reported bugs the the and the projects are pretty similar. How is they different?

Axis2: Have more active committers have both Java and C/C + + implementations have a sponsoring company (WSO2) are perhaps more widely Known have completed a major codebase change and are moving towards stability (but are not as stable as Axis1 yet) Performanc E is comparable to XFire

XFire: is thought to being easier to use have more Clearly-written documentation are currently fairly stable performance is much Bette R than Axis1 and equivalent to Axis2 in most cases

However, there is one major issue that makes Axis2 preferable over XFire at this time:on July 22, 2006, The XFire team announced that in XFire 2 they would is merging codebases with the Celtix framework and joining the Apache Software Foundation as Celtixfire. One of the stated Non-goals for this migration stated by the team are backwards compatibility with the current XFi Re code base-meaning this developers who write new applications using the XFire 1.x framework is going to be facing a sit Uation similar to the one faced by Axis developers when that team dropped Axis1 and began Axis2. Since Axis2 have already completed this transition it makes sense not to adopt XFire for new projects at this time.

Note from XFire Author: XFire Services is deployable inside CXF with little/no modification for most people. Your XML deployment descriptors and/or Your usage of the XFire APIs Wlil need to change though. Hoewver, the APIs in CXF is very similar to the XFire APIs. It isn't a major departure for the most part!

Once The Celtixfire migration is complete, however, and the new version of the software have had the chance to mature, this Comparison needs to be revisited.