celix-commits mailing list archives

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

     [ https://issues.apache.org/jira/browse/CELIX-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Menno van der Graaf updated CELIX-342:
--------------------------------------
    Priority: Minor  (was: Trivial)

> Bundle Manifest unused
> ----------------------
>
>                 Key: CELIX-342
>                 URL: https://issues.apache.org/jira/browse/CELIX-342
>             Project: Celix
>          Issue Type: Improvement
>          Components: Framework
>            Reporter: Menno van der Graaf
>            Priority: Minor
>
> 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
(v6.3.4#6332)

Mime
View raw message