[jira] Resolved: (TUSCANY-2732) Separate Tuscany API extensions from OSOA API

["Simon Laws (JIRA)" <de...@tuscany.apache.org>]

     [ https://issues.apache.org/jira/browse/TUSCANY-2732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Simon Laws resolved TUSCANY-2732.
---------------------------------

    Resolution: Fixed

Change committed to 1.4 and 1.x

> Separate Tuscany API extensions from OSOA API
> ---------------------------------------------
>
>                 Key: TUSCANY-2732
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-2732
>             Project: Tuscany
>          Issue Type: Bug
>    Affects Versions: Java-SCA-1.4
>         Environment: All
>            Reporter: Simon Laws
>            Assignee: Simon Laws
>             Fix For: Java-SCA-1.4
>
>
> A while back I checked the patch for TUSCANY-2281 in and part of this change was the extension of the ComponentContext API. This would seem to be incompatible with the spec license so I would like to propose a further change;
> 1/ Create a ComponentContextExtension interface which extends ComponentContext and holds the new APIs for retrieving reference collections.
> 2/ Have the RuntimeComponentContext extend the CompoentContextExtension interface
> 3/ When you need to use the new APIs you have to cast to the ComponentContextExtension
> Collection<Crawler> crawlers = ((ComponentContextExtension)componentContext).getServices(Crawler.class, "crawlers");
> As an optimization we could look at having the injectors inject ComponentContextExtension if this is specified to remove the need to do the cast.
> See discussion here (http://www.mail-archive.com/dev%40tuscany.apache.org/msg03999.html)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.