[
https://issues.apache.org/jira/browse/ARIES-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14661848#comment-14661848
]
John Ross commented on ARIES-1368:
----------------------------------
I believe this issue would manifest itself when the Subsystem-Content header is
generated by the system and the fragments are provided by a remote repository.
The system would be searching for a resource of type osgi.bundle rather than
osgi.fragment, and presumably the remote repository would have the correct type.
Another manifestation would be when the ESA provider specifies the
Subsystem-Content header themselves using the correct type and packages the
fragment in the ESA itself. In this case, the system would be searching for a
resource of type osgi.fragment, but the type would actually be osgi.bundle in
the local repository.
I believe everything would work correctly if (1) the Subsystem-Content header
is generated by the system, and (2) the fragments are packaged as part of the
ESA.
> BundleResource is not able to compute capabilities for fragments
> ----------------------------------------------------------------
>
> Key: ARIES-1368
> URL: https://issues.apache.org/jira/browse/ARIES-1368
> Project: Aries
> Issue Type: Bug
> Components: Subsystem
> Affects Versions: subsystem-core-1.2.0
> Reporter: Wouter Bancken
> Attachments:
> OsgiIdentityCapability.OsgiIdentityCapability(Resource,BundleManifest)-CallHierarchy.jpg
>
>
> The computeOsgiIdentityCapability method of the BundleResource is not able to
> compute capabilities for fragments (only for bundles).
> This is caused by the fact that the BundleResource is hardcoded to always
> assume a type of osgi.bundle without inspecting the manifest.
> Link to mailinglist thread:
> http://mail-archives.apache.org/mod_mbox/aries-user/201508.mbox/%3CCAL5nZgTOVhdAPYYFOmuV%3DPquAz1a4n_D1Rd3RBrTfu2znCSjKA%40mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
