Hi, I have also run into this issue. I think there is a bug in Karaf 4.2.0 related to blueprint namespace loading. It does not happen all the time, but when it is the case, the solution is to manually restart bundle org.apache.aries.transaction.blueprint-2.1.0.
Regards, -- Nicolas Dutertry -----Message d'origine----- De : ceugster [mailto:[email protected]] Envoyé : mercredi 6 juin 2018 21:32 À : [email protected] Objet : Re: Unresolved dependency using blueprint transaction Hi JB because I was not sure if I did feature:install of aries-blueprint and transaction in the right order, I installed a clean version of karaf-4.2 and then feature:install aries-blueprint feature:install transactions feature:install eclipselink feature:install my bundles then a bundle:diag showed following: karaf@root()> bundle:diag 75 Herakles Jpa Persistence Bundle (75) ------------------------------------ Status: GracePeriod Blueprint 06.06.18, 21:26 Missing dependencies: (&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://aries.apache.org/xmlns/transactions/v2.0.0)) (&(objectClass=org.apache.aries.blueprint.NamespaceHandler)(osgi.service.blueprint.namespace=http://aries.apache.org/xmlns/jpa/v2.0.0)) it seems even worse than before!? Do you have an idea, what could be the solution to this? Thank you! Christian -- Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html
