[forge-issues] [JBoss JIRA] (FORGE-770) Ability to restrict ServiceRegistry and AddonRegistry services by addon dependency version

[George Gastaldi (JIRA)]

     [ https://issues.jboss.org/browse/FORGE-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

George Gastaldi updated FORGE-770:
----------------------------------

    Fix Version/s: 2.0.0.Alpha4
                       (was: 2.0.0.Alpha3)

    
> Ability to restrict ServiceRegistry and AddonRegistry services by addon dependency version 
> -------------------------------------------------------------------------------------------
>
>                 Key: FORGE-770
>                 URL: https://issues.jboss.org/browse/FORGE-770
>             Project: Forge
>          Issue Type: Story
>          Components: Container
>    Affects Versions: 2.0.0.Alpha1
>            Reporter: Lincoln Baxter III
>            Assignee: Lincoln Baxter III
>             Fix For: 2.0.0.Alpha4
>
>
> Like in OSGi (shudder,) when looking up services from the ServiceRegistry, it should be possible to require that services retrieved from the ServiceRegistry be locked to a specific addon API version (via addon-dependency/classloader mapping.)
> {code}
> (A) -> (B, v1)
>     -> Service 1
> (B, v2)
>     -> Service 1v2
>     -> Service 2v1
> {code}
> A should receive only the instance of Service 1 from (B, v1)

--
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