[CONF] Apache CXF Documentation > 2.5 Migration Guide

[confluence]

2.5 Migration Guide Page edited by Aki Yoshida Changes (3) h3. New Features * WS-RM is being updated to support 1.1 * WS-RM components are fully JMX instrumented * WS-RM is being updated to support 1.1. Also included are some feature improvements such as sequence demarcation by WS-RM client. * WS-RM components are fully JMX instrumented. Various status information about the WS-RM processing such as sequences, retries, acknowledgments can be monitored over JMX. * WS-MetadataExchange support for server side. CXF services will now respond properly to WS-MEX requests. ... * The default bus ID used for the Bus MBean servers when running in OSGi now contains the bundle context SymbolicName to make identifying the appropriate Bus easier. * Many calls that can result in Security checks are now wrapped via AccessControll.doPrivileged calls which can allow finer grained control of the permissions that CXF requires. See https://issues.apache.org/jira/browse/CXF-2683 . * An empty partial response message will be returned as an HTTP 202 response with no content instead of an HTTP 200 with an empty SOAP body message. ... Full Content New Features WS-RM is being updated to support 1.1. Also included are some feature improvements such as sequence demarcation by WS-RM client. WS-RM components are fully JMX instrumented. Various status information about the WS-RM processing such as sequences, retries, acknowledgments can be monitored over JMX. WS-MetadataExchange support for server side. CXF services will now respond properly to WS-MEX requests. Removed modules All the JBI related modules have been removed from CXF. If using CXF with JBI, it's recommended to use the ServiceMix CXF JBI components. Any code that those modules needed from past versions of CXF will be moved into those ServiceMix components. API Changes Runtime Changes If a MBeanServer is available in the Spring context or as an OSGi server (when running in OSGi), the InstrumentationManger will be automatically enabled and will use that MBeanServer and the CXF MBeans will be registered. The default bus ID used for the Bus MBean servers when running in OSGi now contains the bundle context SymbolicName to make identifying the appropriate Bus easier. Many calls that can result in Security checks are now wrapped via AccessControll.doPrivileged calls which can allow finer grained control of the permissions that CXF requires. See https://issues.apache.org/jira/browse/CXF-2683 . An empty partial response message will be returned as an HTTP 202 response with no content instead of an HTTP 200 with an empty SOAP body message. Property Changes Change Notification Preferences View Online | View Changes | Add Comment