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

[Lincoln Baxter III (JIRA)]

    [ https://issues.jboss.org/browse/FORGE-770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788515#comment-12788515 ] 

Lincoln Baxter III commented on FORGE-770:
------------------------------------------

Solved by always depending on the highest version of an installed Addon by name. The container builds graphs to represent the addon state, and links the appropriate versions.

The restriction component is accomplished by a new feature called AddonView - this allows the API consumer to request a view of the configured AddonRepository instances and obtain addon instances from one or several specific repositories, while the master or ROOT view continues to operate on all repositories.
                
> Ability to restrict ServiceRegistry and AddonRegistry services by version
> -------------------------------------------------------------------------
>
>                 Key: FORGE-770
>                 URL: https://issues.jboss.org/browse/FORGE-770
>             Project: Forge
>          Issue Type: Feature Request
>          Components: Container
>    Affects Versions: 2.0.0.Alpha1
>            Reporter: Lincoln Baxter III
>            Assignee: Lincoln Baxter III
>             Fix For: 2.0.0.Alpha7
>
>
> 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