aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Ross (JIRA)" <>
Subject [jira] [Commented] (ARIES-952) Break dependency of Aries Subsystems on Aries Blueprint
Date Mon, 01 Jul 2013 20:55:20 GMT


John Ross commented on ARIES-952:

I think the right solution for this issue is to make the ModelledResourceManager service dependency

Those not wishing to use Aries Blueprint are then free to not install the org.apache.aries.application.modeller,
org.apache.aries.blueprint, and org.apache.aries.proxy bundles.

If you don't care about service capabilities and requirements being part of the resolution
at subsystem install time, then you're done.

If you do care, and do not wish to use Aries Blueprint, then you must provide an implementation
of the org.apache.aries.application.modelling API and register a ModelledResourceManager service.
> Break dependency of Aries Subsystems on Aries Blueprint
> -------------------------------------------------------
>                 Key: ARIES-952
>                 URL:
>             Project: Aries
>          Issue Type: Improvement
>          Components: Application, Subsystem
>            Reporter: Glyn Normington
> Aries Subsystems currently has a hard dependency on Aries Blueprint (AB).
> When running Aries Subsystems in an environment where there is already a Blueprint implementation,
we end up with duplicate Blueprint extenders, which is of course a recipe for disaster.
> One such environment is the Virgo kernel. Virgo depends on Gemini Blueprint (GB) because
it uses the Spring DM function provided by GB. So it's not possible to substitute AB for GB.
> So the requirement is to make it possible to run Aries Subsystems with GB. Admittedly
this may involve adding some GB code to support resource modelling for Blueprint, but that
should be separated from the AB implementation.
> To reproduce the problematic environment, see
and follow the instructions in The web admin console can then be used to observe
both GB and AB extenders running in the Virgo user region. Also, the nature of the hard dependency
can be observed by deleting the Aries Blueprint core bundle from the Virgo kernel's repository/usr
directory and restarting Virgo - the modeller no longer resolves:
> missing constraint in bundle <org.apache.aries.application.modeller_1.0.1.SNAPSHOT>
>              constraint: <Import-Package:;

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