[forge-issues] [JBoss JIRA] (FORGE-770) Ability to restrict ServiceRegistry and AddonRegistry services by addon dependency version
Lincoln Baxter III (JIRA)
jira-events at lists.jboss.org
Wed Apr 3 22:28:43 EDT 2013
[ https://issues.jboss.org/browse/FORGE-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lincoln Baxter III reassigned FORGE-770:
----------------------------------------
Assignee: Lincoln Baxter III
> 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.Alpha2
>
>
> 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
More information about the forge-issues
mailing list