[TUSCANY-2732] Separate Tuscany API extensions from OSOA API

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Java-SCA-1.4
• Fix Version/s: Java-SCA-1.4
• Environment: All
• Assignee: Simon Laws
• Reporter: Simon Laws
• Created: 09/Dec/08 10:31
• Updated: 19/Sep/10 11:30
• Resolved: 10/Dec/08 18:05

Description

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)

Issue Links

• blocks: TUSCANY-2281 How to create ServiceReferences for references using multiplicity="1..n"