karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-3918) An installed blueprint.xml has always been updated and restarted when install another unrelated feature
Date Wed, 14 Oct 2015 14:44:05 GMT

    [ https://issues.apache.org/jira/browse/KARAF-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14957030#comment-14957030
] 

Christian Schneider commented on KARAF-3918:
--------------------------------------------

I think this could be related with the blueprint deployer creating a bundle using Dynamic-Import:*.
There are known issues with ActiveMQ as well as with Camel where such bundles are wired to
packages dynamically during the extension detection of ActiveMQ and Camel. These issues are
fixed with the newest versions of ActiveMQ and Camel but may still apply to your deployment.


Do you think that might apply to you? 

> An installed blueprint.xml has always been updated and restarted when install another
unrelated feature
> -------------------------------------------------------------------------------------------------------
>
>                 Key: KARAF-3918
>                 URL: https://issues.apache.org/jira/browse/KARAF-3918
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-feature
>    Affects Versions: 4.0.0
>         Environment: Java 7
>            Reporter: Xilai Dai
>            Assignee: Jean-Baptiste Onofré
>             Fix For: 4.0.3
>
>
> There is an installed blueprint.xml. (by install -s blueprint:mvn:org.abc/my-project/1.0-SNAPSHOT/xml,
or deploy this blueprint.xml into deploy folder).
> then, if you do feature:install xxxx, to install some other feature (no dependencies
to the blueprint.xml above), the installed blueprint.xml will always be updated and restarted,
that's not expected behavious.
> After checking with org.apache.karaf.features.internal.service.Deployer class, I found
that the old checksum will only be calculated in case of url start with "jar:" (Line 1159),
so in case of the url start with "blueprint:", the new checksum will never equal with old
checksum, then it will be put into deployment.toUpdate Map.
> The Deployer class should be fixed for "blueprint:" deployment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message