Page Edited :
CXF :
2.2 Migration Guide
2.2 Migration Guide has been edited by Daniel Kulp (Mar 09, 2009). Content:API changesAegisThe building of the Schema in the Aegis type system has changed from using JDom to using XmlSchema directly. This avoids a 3 hop JDOM -> DOM -> XmlSchema performance penalty, but requires changes to any custom Aegis type objects. JAX-RSThe JAX-RS runtime/api's have been updated to JAX-RS 1.0 level from 0.8. Some code written for 0.8 may need modifications to run with the 1.0 level. Runtime changesPolicy engineThe Policy engine now defaults to on instead of off. Thus, if you are using WSDL that contains WS-Policy assertions, those assertions will now be evaluated by default. Config changesJMSThe default value for the useJms11 flag has changed to true so CXF will use the JMS 1.1 API's when possible. If you are using a JMS 1.0 provider, you will need to adjust the configuration to set this to false to force the use of the 1.0 API's. Tooling changesMaven WSDL2Java pluginThe default location for the sourceRoot variable where the code is generated into is now "$ Unknown macro: {project.build.directory} /generated-sources/cxf" to match the maven best practices for plugins. |
Unsubscribe or edit your notifications preferences