THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- 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
- The AlternativeSelector.selectAlternative method for selecting the Policy alternative to use now requires a new List<List<Assertion>> parameter which, on the server side, is the list of Alternatives that the incoming request matched. The AlternativeSelector can use that to aid in selecting the best response alternative to use.
- The PolicyEngine.getEffectiveServerResponsePolicy now takes an additional parameter of the incoming policy alternatives that were matched. It can be null for the previous behavior.
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.
...