aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Watson (JIRA)" <>
Subject [jira] [Updated] (ARIES-997) Support for the Aries Application header Application-ImportService
Date Fri, 04 Jan 2013 21:20:14 GMT


Thomas Watson updated ARIES-997:

    Attachment: org.apache.aries.subsystem.core.patch

Here is a possible fix.  This solution adds a new "fake" resource the the LocalRepository
for subsystems that are being installed which have an Application-ImportService header.  The
fake resource has no requirements and only contains osgi.service capabilities that can be
used to satisfy the imported services specified by the Application-ImportService header. 

These capabilities can then be used during resolution to help resolve and osgi.service requirements
from content resources when provisioning the ESA.

I introduced a new internal resource type (aries.subsystem.fake.resource) that is used to
indicate to the ResourceInstaller to ignore the fake resources during installation.
> Support for the Aries Application header Application-ImportService
> ------------------------------------------------------------------
>                 Key: ARIES-997
>                 URL:
>             Project: Aries
>          Issue Type: Bug
>          Components: Subsystem
>            Reporter: Thomas Watson
>         Attachments: org.apache.aries.subsystem.core.patch
> The old Aries Application support (implemented using equinox composite bundles) has support
for a header Application-ImportService.  This header has a different intention than the subsystems
specified Subsystem-ImportService header.
> The Subsystem-ImportService header is intended to be used by composite subsystem types
only and is used to specify the import sharing policy for services.  For subsystems the imported
services are expected to be provided by some provider (bundle) which is visible in the parent
subsystem of the composite which is importing the service.
> The Application-ImportService header on the other hand is used to specify services which
are expected to be provided by some remote service technology, for example SCA.  For Aries
applications no resources are provisioned to satisfy the service requirements specified by
the Application-ImportService header.  Instead, at provisioning time the Aries application
support mocks up a resource that provides service capabilities that can be used to resolve
service requirements from the resources (bundles) included in an EBA that is being provisioned.
> This issue proposes that the Aries Subsystem implementation should add support for the
Application-ImportService header that is similar in behavior to the Aries Application support.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message