[CONF] Apache CXF Documentation > 3.0 Migration Guide

[confluence]

3.0 Migration Guide Page edited by Christian Schneider Changes (1) ... * POSSIBLY update various API's to pass in the Bus (or other objects) if needed instead of holding it as an instance variable. That would allow singleton instances for things like the transports and such. For example, it would be good to register a "FooCXFTransport" as an OSGi service that we could lookup later. Right now, we couldn't do that unless you only used a global bus, which isn't exactly what the purpose of the Bus is. * Move feature impls out of API and into core. Currently feature and interceptor classes are in different packages. Which makes it difficult to modularize them. So we should rather have one package per feature where feature class and interceptor classes are located Full Content 3.0 Migration Guide Right now, 3.0 is in VERY early planning stages. This page is mostly collecting lists of things we are planning on changing. It is by no means an exhaustive list and it may completely change depending on what gets done and such. Combine common-utilities/api/core into just a cxf-kernel or similar. Pull the "wsdl" specific stuff from kernel into a webservices base package that the webservices related things can pull and jaxrs doesn't have to. Resolve all the split package things that prevent the OSGi bundling from working well. Likely move some of the other Abstract classes and such from kernel. For example, we now have a transports-common module. Move the AbstractDestination and stuff there. Go through all the @Deprecated things and remove them. Likewise, remove unused method params (I know there are a couple on the Destination API) and such. POSSIBLY update various API's to pass in the Bus (or other objects) if needed instead of holding it as an instance variable. That would allow singleton instances for things like the transports and such. For example, it would be good to register a "FooCXFTransport" as an OSGi service that we could lookup later. Right now, we couldn't do that unless you only used a global bus, which isn't exactly what the purpose of the Bus is. Move feature impls out of API and into core. Currently feature and interceptor classes are in different packages. Which makes it difficult to modularize them. So we should rather have one package per feature where feature class and interceptor classes are located Change Notification Preferences View Online | View Changes | Add Comment