Raible's Wiki: AppFuseXFire

At line 16 changed 5 lines.

You may wonder, why I bother to write a howto for XFire, given that there is already one for Axis, the far more widely used Webservice framework.

But you may wonder as well, why the codehaus people bother writing XFire at all, years after Axis was published in the first place.

The reason for the latter, in my personal opinion, is that Axis 1 has some shortfalls. Namely dealing with Collections and it is not so easy to plug in another XML binding framework.

Why should you not be comfortable with the built in XML binding? Because it is not as powerful as for example XmlBeans. You have to limit your application to a subset of what's possible with webservices.

Another, in some cases important benefit is performance (in terms of speed), that is because the next generation webservice frameworks (like Axis 2 and XFire) are based an [StAX|http://www.xml.com/pub/a/2003/09/17/stax.html], the Streaming Api for Xml.

You may wonder, why I bother to write a howto for XFire, given that there is already one for Axis, the far more widely used

Webservice framework. But you may wonder as well, why the codehaus people bother writing XFire at all, years after Axis was

published in the first place.

The reason for the latter, in my personal opinion, is that Axis 1 has some shortfalls. Namely dealing with Collections and

it is not so easy to plug in another XML binding framework.

Why should you not be comfortable with the built in XML binding? Because it is not as powerful as for example XmlBeans.

You have to limit your application to a subset of what's possible with webservices.

Another, in some cases important benefit is performance (in terms of speed), that is because the next generation webservice

frameworks (like Axis 2 and XFire) are based an [StAX|http://www.xml.com/pub/a/2003/09/17/stax.html], the Streaming Api for Xml.

At line 22 changed 1 line.

Axis 2 is (as well as XFire) in pre 1.0 state, XFire is, however, just a few days away from it's 1.0 as of Jan 2006. My motivation to use XFire instead of Axis 2 is, that I started using it, was successful in short time, and just stuck with it, becoming a committer of the project.

Axis 2 is (as well as XFire) in pre 1.0 state, XFire is, however, just a few days away from it's 1.0 as of Feb 2006.

My motivation to use XFire instead of Axis 2 is, that I started using it, was successful in short time, and just stuck with it,

becoming a committer of the project.

At line 24 changed 1 line.

There's work in progress to automate the process of plugging in XFire into AppFuse (via an extras package), you'll find the first shot version attached to this page as [zip|http://raibledesigns.com/wiki/attach/AppFuseAxis/extras-xfire.zip].

There's work in progress to automate the process of plugging in XFire into AppFuse (via an extras package), you'll find the

first shot version attached to this page as [zip|http://raibledesigns.com/wiki/attach/AppFuseAxis/extras-xfire.zip].

At line 26 changed 1 line.

All that's described on this page is performed by an ant-task in this package. Expand it in the extras folder of your project, go into the folder xfire-webservice with a shell and do an

All that's described on this page is performed by an ant-task in this package. Expand it in the extras folder of your project,

go into the folder xfire-webservice with a shell and do an

Raible's Wiki

AppFuse

Other Applications

AppFuseXFire