The XFire team is proud to announce the 1.0-M6 release! XFire is a next-generation java SOAP framework. XFire makes service oriented development approachable through its easy to use API and support for standards. It is also highly performant since it is built on a low memory StAX based model.
This release features many improvements:
- JAXB 1.1 and 2.0 support
- Client and Server stub generation
- Improved XML configuration
- Improved Spring support
- Improved Client support
- Improved schema customization for Aegis binding
- Many bug fixes
Many people are already using XFire today and realizing its performance and ease of use benefits. Why not download it and see for yourself?
Binary Distribution in zip package
Jar of all XFire modules (also see the Dependency Guide)
Upgrading to M6 from M5
- YOM has replaced with JDOM. You will need to remove your YOM jars from your classpath and add the JDOM 1.0 jar. This jar can be found here.
- The services.xml format has changed! Instead of assembling services by parsing XML, we let a new tool, XBean do it for us. This means you need to a dependency on XBean and on the spring-core jar to your classpath. To read more about how the services.xml format works, read the XML Configuration page. The major changes in the format are:
- <xfire> is no longer the root element. It is <beans xmlns="http://xfire.codehaus.org/config/1.0">
- You no longer need a <services> element to wrap your <service> elements.
- The XMLBeans client support has been removed. Now we have a new Client API.
- The "service" property on XFireExporter and ServiceBean has been renamed to "serviceBean".
M6a fixes a bug in the geoip-client example in M6.