[
https://issues.apache.org/jira/browse/SM-2279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13988150#comment-13988150
]
Gert Vanthienen commented on SM-2279:
-------------------------------------
It took me some debugging yesterday eventing to figure out why the change in
startlevel in the startup.properties file actually works. It turns out that
for the bundles that are already active in the container when the OBR
implementation is installed, it looks at the actual services that have been
published by a bundle instead of relying on the {{Export-Service}} header for
this information.
Anyway, changing the runlevel to anything higher than the {{proxy-impl}} bundle
will do the trick, so I think that would be the best solution for this issue
until the ARIES-1182 one gets fixed.
> The jndi feature can not be installed
> -------------------------------------
>
> Key: SM-2279
> URL: https://issues.apache.org/jira/browse/SM-2279
> Project: ServiceMix
> Issue Type: Bug
> Components: assemblies
> Affects Versions: 5.0.0
> Reporter: Krzysztof Sobkowiak
> Fix For: 5.0.1, 5.1.0, 6.0.0
>
>
> Installation of the jndi feature ends with following error
> {code}
> karaf@root> features:install jndi
> Error executing command: Can not resolve feature:
> Unsatisfied requirement(s):
> ---------------------------
> service:(service=org.apache.aries.proxy.ProxyManager)
> Apache Karaf :: JNDI :: Core
> {code}
> Cfr:
> http://servicemix.396122.n5.nabble.com/Feature-Install-Errors-in-SMX-5-0-0-td5719921.html
--
This message was sent by Atlassian JIRA
(v6.2#6252)
