[
https://issues.apache.org/jira/browse/ARIES-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom De Wolf updated ARIES-1368:
---
Attachment: test-service-fragment-subsystem-1.0.1-SNAPSHOT.esa
It is the Aries ESA plugin at
http://aries.apache.org/modules/esamavenpluginproject.html
https://github.com/apache/aries/tree/trunk/esa-maven-plugin
Installing the attached subsystem including a fragment with the install gogo
command results in the stacktrace below. Thus the included fragment is not
found. The gogo commands are the ones included in the aries code base at:
https://github.com/apache/aries/tree/trunk/subsystem/subsystem-gogo-command
Cause: OsgiIdentityCapability identifies all bundles as osgi.bundle via the
osgi.identity capability, it should check for fragments and use osgi.fragment.
{code}
install
file:/Users/tom/Downloads/test-service-fragment-subsystem-1.0.1-SNAPSHOT.esa
...
Caused by: org.osgi.service.subsystem.SubsystemException: A required content
resource could not be found. This means the resource was either missing or not
recognized as a supported resource format due to, for example, an invalid
bundle manifest or blueprint XML file. Turn on debug logging for more
information. The resource was:
org.apache.aries.subsystem.core.archive.SubsystemContentRequirement:
namespace=osgi.identity, attributes={},
directives={filter=((osgi.identity=be.aca.test-service-fragment)(type=osgi.fragment)((version=1.0.1.SNAPSHOT)(version=1.0.1.SNAPSHOT)))},
resource=org.apache.aries.subsystem.core.internal.SubsystemResource@9780e9f1
at
org.apache.aries.subsystem.core.internal.SubsystemResource.computeContentResources(SubsystemResource.java:384)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.computeContentResources(SubsystemResource.java:360)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.init(SubsystemResource.java:99)
at
org.apache.aries.subsystem.core.internal.SubsystemResource.init(SubsystemResource.java:92)
at
org.apache.aries.subsystem.core.internal.InstallAction.createSubsystemResource(InstallAction.java:134)
at
org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:55)
at
org.apache.aries.subsystem.core.internal.InstallAction.run(InstallAction.java:33)
at java.security.AccessController.doPrivileged(Native Method)
at
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:621)
at
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:259)
at
org.apache.aries.subsystem.core.internal.BasicSubsystem.install(BasicSubsystem.java:63)
... 30 more
g!
{code}
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,
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)
