karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (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 Tue, 01 Dec 2015 16:53:10 GMT

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

Guillaume Nodet commented on KARAF-3918:

Fwiw, both spring and blueprint deployers do scan the xml for bean classes and automatically
generate import packages for those.  For blueprint, this may be sufficient.  For spring, one
also needs to import the various custom namespace packages, and those can't easily be discovered.
 Fortunately, this should be fixed when we switch to the spring support from Aries.
For blueprint, we may already be able to remove the dynamic imports, it needs to be tested
a bit more.
And given there's no embedded classes, we don't really need to run BND, we simply run the
xslt, which is/should be the same as the one used in the maven bundle plugin to discover the

> 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é
> 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

View raw message