[
https://issues.apache.org/jira/browse/ARIES-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697142#comment-13697142
]
John Ross commented on ARIES-952:
---------------------------------
Strictly speaking, the subsystems core bundle only has a dependency on the
org.apache.aries.application.api bundle and an
org.apache.aries.application.modelling.ModelledResourceManager service.
The README shows one set of bundles that are known to provide all needed
dependencies. Many of the dependencies are based on API so there might be other
acceptable lists. The list includes the org.apache.aries.application.modeller
bundle because it's known to provide an implementation of
org.apache.aries.application.modelling along with a ModelledResourceManager
service. The modeller bundle necessitates org.apache.aries.blueprint which, in
turn, requires org.apache.aries.proxy.
Removing these bundles from the runtime and replacing them with some other
implementation of org.apache.aries.application.modelling that provides a
ModelledResourceManager service capable of delivering service capabilities and
requirements from a source other than Aries Blueprint should work with the
current subsystems implementation.
> Break dependency of Aries Subsystems on Aries Blueprint
> -------------------------------------------------------
>
> Key: ARIES-952
> URL: https://issues.apache.org/jira/browse/ARIES-952
> 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
> https://github.com/glyn/aries-subsystems-on-virgo-kernel and follow the
> instructions in README.md. 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:
> org.apache.aries.blueprint.services; version="[1.0.0,2.0.0)">
--
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: http://www.atlassian.com/software/jira
