[ https://issues.apache.org/jira/browse/ARIES-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14646271#comment-14646271 ]
Christian Schneider commented on ARIES-791: ------------------------------------------- Is this issue still relevant? I think cxf works fine with current blueprint versions. > Blueprint 0.4 is not backwords compatible in ways that break CXF > ---------------------------------------------------------------- > > Key: ARIES-791 > URL: https://issues.apache.org/jira/browse/ARIES-791 > Project: Aries > Issue Type: Bug > Components: Blueprint > Reporter: Daniel Kulp > Assignee: Daniel Kulp > > Some of the changes in 0.4 of blueprint cause CXF to break. These include: > 1) Marking container, di, and util as private. CXF needs these to configure > objects. (see ARIES-790) > 2) Removal of BundleDelegatingClassLoader > 3) Moving of ExtendedBlueprintContainer into services subpackage > We really need a version of blueprint that tries to be as backwords > compatible as possible (to allow existing users to upgrade without breaking > applications), but also provide the new API's (deprecate the old ones) so > that projects like CXF can update to new API's. When 0.4.1 is out for a > while and most users/dependencies have updated, THEN remove the breaking > changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)