celix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pepijn Noltes (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CELIX-342) Bundle Manifest unused
Date Tue, 26 Jan 2016 14:49:40 GMT

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

Pepijn Noltes commented on CELIX-342:

Yes remove the manifest from bundle. 

Although manifest headers should be retrievable by the bundle api (see https://osgi.org/javadoc/r6/core/index.html)
storing a bundle at the bundle revision is more logical. 
the bundle api retrieve it's manifest info from the current bundle revision. I 

> Bundle Manifest unused
> ----------------------
>                 Key: CELIX-342
>                 URL: https://issues.apache.org/jira/browse/CELIX-342
>             Project: Celix
>          Issue Type: Question
>          Components: Framework
>            Reporter: Menno van der Graaf
>            Priority: Trivial
> After some confusion during a debug session, i looked into why the "bundle->manifest"
pointer was always NULL. It turns out this is initialized at creation, then never assigned.
Yet the framework works fine? Apparently the manifest files distributed in each bundle ARE
used, by the bundle revision. Each bundle revision holds a manifest, that is then used for
module creation and data acquisition.
> The question then remains, is this construct correct? in which case I would propose to
delete the "bundle->manifest" field, since it causes confusion (and Celix could do with
a bit less confusion).

This message was sent by Atlassian JIRA

View raw message