XFire Migration has been edited by Dan Diephouse (Nov 09, 2006).

(View changes)

Content:

Completed Functionality and CXF analogues

XFire Feature CXF Analogue
Aegis Binding In the process of being ported...
Configurable Servlet CXFServlet will do simple mappings, but doesn't contain Spring support. Still exploring options here.
Eclipse Plugin
Not ported yet
HTTP Transport Completed
JMS Transport Completed
JAX-WS/JSR-181 Annotation Support Completed
JAXB Completed
MTOM
Completed, although needs more interop testing
services.xml Spring 2 XML will be supported for easy configuration
Spring: XFireClientFactoryBean Not ported yet
Spring: XFireExporter Not ported yet
Spring: ServiceBean Completed. See ServerFactoryBean and JaxWsServerFactoryBean.
WS-Addressing
We're now using the WS-Addressing support from Celtix which is much more advanced.
WS-Security Not ported

Should I Migrate Yet?

For most XFire users, the answer is NO right now. With M1 we've focused on the core functionality and architecture. M2 will contain most of the features XFire users have come to rely on such as Aegis or our helper Spring beans.

Migrating

 

Reply via email to