THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
XFire Feature | CXF Analogue |
|---|---|
Aegis Binding In | the process of being ported... Mostly Ported. Exceptions are still not supported |
Configurable Servlet | No services.xml supported yet, but works with normal Spring format. See the Servlet Transport page. |
Eclipse Plugin | Not ported yet |
HTTP Transport | Completed Ported. |
JMS Transport | Completed Ported. |
JAX-WS/JSR-181 Annotation Support | In progress. Work is ongoing to ensure we pass the TCKs. |
JAXB Completed | Ported. |
MTOM | , although needs more interop testing Ported. |
services.xml | Spring 2 XML will be supported for easy configuration. See the Configuration section. |
Spring: XFireClientFactoryBean Not ported yet | See the ClientProxyFactoryBean and JaxWsProxyFactoryBean. |
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 | Ported. See the WS-Security page. |
XMLBeans | Not ported. Will be supported in CXF 2.1 |
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.
...