aries-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "gembin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARIES-952) Break dependency of Aries Subsystems on Aries Blueprint
Date Sat, 29 Jun 2013 16:54:20 GMT

    [ https://issues.apache.org/jira/browse/ARIES-952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13696150#comment-13696150
] 

gembin commented on ARIES-952:
------------------------------

+1

Could some given some instructions how to remove the dependency on Aries Blueprint?  i would
like to have a try.

i take a quick look at the code of org.apache.aries.application.modeller, and found it depends
on org.apache.aries.blueprint.services.ParserService and org.apache.aries.blueprint.ComponentDefinitionRegistry

and i just dont understand why it wants to parse the blueprint services of the bundles of
a subsystem.

is there any relationship between subsystem service & blueprint service?
                
> 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

Mime
View raw message