Java SOAP Framework XFire 1.2 Released

Posted by Scott Delap on Aug 28, 2006 05:27 PM

Community

Java,

SOA

Topics

WS Standards ,

Web Services

Tags

WSDL ,

XFire ,

SOAP ,

WS-Reliable Messaging ,

XML

XFire, the high performance Java SOAP framework from Codehaus has released version 1.2, the last version before the 2.0 release which will be merged with ObjectWeb's Celtix project as a new Apache project called CeltiXfire.    XFire includes such features as Spring integration, JBI support, and pluggable bindings for POJOs, JAXB, and XMLBeans. Improvements since version 1.1:

• JiBX databinding support
• HTTP GZIP Support
• WSDL2Java now auto generates services.xml
• Aegis binding inheritance support
• Option to disable server stub generation

InfoQ sat down with project committer Dan Diephouse to talk about the 1.2 release. In regards to the advantages of using XFire over other options like Axis, Diephouse responded:

The comment that I most often here is that XFire makes building web services easy. Things like our Spring integration makes XFire very straightforward to integrate into a lot of applications. XFire also has a very extensible and usable API, making it easy to embed, hack and reuse. Another big difference between XFire and others is the performance. If you're still using something like Axis 1.x, XFire can give you a 5x boost in performance.

Expanding on why XFire is faster:

XFire is based on StAX, which is the Java streaming XML API. Using this API we are able to parse the XML one chunk at a time. This is much faster and more memory efficient as we don't need to create a DOM for the XML.

As far as common use cases include:

XFire is most commonly used to build and consume web services. You may be trying to build a more service oriented architecture. XFire can help you build the services part by exposing services through WSDL & SOAP. Or you may be building services to do some cross language integration. Nearly very language speaks SOAP & WSDL. We have people doing integration with .NET, Python, Ruby, Perl, PHP, and more!

On XFire vs. Glassfish's JAX-WS implementation. Diephouse explained that XFire has a broader set of goals than Glassfish such as pluggable databindings and Spring integration out of the box.   

Going forward, XFire will merge with ObjectWeb's Celtix team as the projects goals were found to be very similar.  The new project will be hosted at Apache and is called CeltiXfire (CXF). "For the XFire community it can be thought of as XFire 2.0." CXF will include REST, WS-ReliableMessaging, and WS-Policy support.   Development on the project has already begun.

1. Back to top

   jibx

   Aug 29, 2006 1:31 AM by anjan bacchu

   hi there, i get a 404 for your jibx link. http://www.infoq.com/errorna.jsp BR, ~A

   Reply

2. Back to top

   mailing list not created yet

   Aug 29, 2006 1:47 AM by anjan bacchu

   hi there, i tried subscribing to the user list and got the following error response. : Sorry, no mailbox here by that name. (#5.1.1) BR, ~A

   Reply

3. Back to top

   Re: jibx

   Aug 29, 2006 2:01 AM by Stefan Tilkov

   Thanks for pointing this out, I fixed the links.

   Reply

4. Back to top

   Re: <cxf-users-subscribe@incubator.apache.org> mailing list n

   Aug 29, 2006 2:02 AM by Stefan Tilkov

   That's a problem with the Apache mailing list; nothing we at InfoQ can do about this ...

   Reply

5. Back to top

   Re: <cxf-users-subscribe@incubator.apache.org> mailing list n

   Aug 29, 2006 2:03 AM by Stefan Tilkov

   That's a problem with the Apache mailling list server; there's nothing we at InfoQ could do about it.

   Reply

6. Back to top

   Re: <cxf-users-subscribe@incubator.apache.org> mailing list n

   Aug 29, 2006 7:54 AM by Dan Diephouse

   hi there, i tried subscribing to the user list and got the following error response. <cxf-users-subscribe@incubator.apache.org>: Sorry, no mailbox here by that name. (#5.1.1) BR, ~A

   Turns out the link on the mailing list page was wrong, its supposed to be cxf-user-subscribe@incubator.apache.org. I've fixed the link on the page, so everything should be good now!

   Reply

• Older >