Page Edited :
CXF :
2.2 Migration Guide
2.2 Migration Guide has been edited by Daniel Kulp (Mar 13, 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. The long deprecated org.codehaus.xfire.aegis.type.java5 annotations have been removed. When migrating apps from XFire, you will need to update to use the JAXB annotations or the equivalents in org.apache.cxf.aegis.type.java5. 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. If you need to turn it off, update your config to include: <cxf:bus>
<cxf:features>
<p:policies enabled="false"/>
</cxf:features>
</cxf:bus>
Note: this only applies if the cxf-rt-policy module is available or if you use the full cxf bundle jar. If you are using the maven modules and don't bring in the cxf-rt-policy artifact, then the policy engine will not be available.
|
Unsubscribe or edit your notifications preferences