[
https://issues.apache.org/jira/browse/ARIES-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14681765#comment-14681765
]
John Ross commented on ARIES-1368:
----------------------------------
I changed line 73 of OsgiIdentityCapability from
IdentityNamespace.TYPE_BUNDLE);
to
manifest.getHeader(Constants.FRAGMENT_HOST) == null ?
IdentityNamespace.TYPE_BUNDLE : IdentityNamespace.TYPE_FRAGMENT);
in order to correctly identify fragments from bundles. Testing for the
existence of the Fragment-Host header is sufficient for identifying a bundle as
a fragment. However, this did not fix the problem. Upon further debugging, it
looks like the Fragment-Host requirement is not being included as part of the
corresponding resource which results in an improper resolution.
> 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.0.0, subsystem-core-1.1.0,
> subsystem-core-1.2.0, subsystem-2.0.2, subsystem-2.0.1
> Reporter: Wouter Bancken
> Assignee: John Ross
> Attachments:
> OsgiIdentityCapability.OsgiIdentityCapability(Resource,BundleManifest)-CallHierarchy.jpg,
> test-service-fragment-subsystem-1.0.1-SNAPSHOT.esa
>
>
> 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)
