[
https://issues.apache.org/jira/browse/SM-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14070830#comment-14070830
]
Benjamin Graf commented on SM-2348:
-----------------------------------
First of all my fault to call spring-dm blueprint. But there are good reasons
to do so. Spring-dm is a dead project and usage should be avoided. I think many
features referencing spring-dm don't really use it any more since aries
blueprint is favorite. But there actually exists many transitive dependencies
to spring-dm. (e.g. camel, activemq, cxf) The reason this causing problems is
the spring-dm extender which similarly works like the blueprint extender
(registers listener). Sometimes this extender interacts with felix and
blueprint which ends in NPEs causing listener stack dying. It was quite hard to
find why bundles sometimes are hanging. spring-dm overriding helps for me.
> Add empty spring-dm feature
> ---------------------------
>
> Key: SM-2348
> URL: https://issues.apache.org/jira/browse/SM-2348
> Project: ServiceMix
> Issue Type: Improvement
> Components: assemblies
> Affects Versions: 5.0.2, 5.1.0
> Reporter: Benjamin Graf
>
> Many feature files like activemq, cxf or camel references spring-dm. This
> causes that normally two blueprint implementations gets installed which
> sometimes can cause "strange" problems. To avoid this behavior the servicemix
> feature file should override karaf
> e.g.
> <feature name="spring-dm" version="1.2.1" resolver="(obr)"/>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
