XFire, an open source soap stack used in SOA, is being fitted with enhancements for security, binary attachments, and XML object binding, the developer of the stack says at TheServerSide Java Symposium conference.
The technology is viewed as an alternative to Apache Axis, a new release that came out recently.
Specifically, Version 1.1 of XFire, due in approximately three weeks, will support the WS-Security specification; MTOM (Message Transmission Optimisation Mechanism) for handling large, binary objects and JiBX, for XML object binding, says Dan Diephouse, developer and president of Envoisolutions.
XFire, written two years ago, provides for Java-based web services’ development. It has featured high performance, ease-of-use and integration with the Spring framework, Diephouse says. Pluggable bindings have also been a key attraction, he says.
“You can use anything to convert XML to objects, whether it be Castor, XMLBeans or JAXB (Java Architecture for XML Binding),” Diephouse says.
A conference attendee and XFire user touted the binding feature. “I like the fact that XFire supports making pluggable bindings,” says Duc Trinh, systems architect at Wells Fargo. Users can replace bindings online, he says.
Although XFire will add WS-Security, Diephouse has issues with the specification. “It just doesn’t scale,” Trinh says.
XFire handles large-object tree collections well, according to Diephouse. It doesn’t support RPC encoding but uses document literal web services, he says.
Apache, meanwhile, announced Axis2 0.95, with its transport framework improvements.
Other features in Axis2 include Axiom, which is an XML object model. XML Infoset support is also featured.
REST (Representational State Transfer) is supported in Axis2 0.95 as well. A WSDL code generation tool for stubs and skeletons is included, as is support for WS-Addressing and a WSS4J module for security. WSS4J is an Apache implementation of WS-Security. Axis2 is an effort to re-implement Axis/Java and Axis/C++ on a new architecture, says Apache.