Handling of self references, was: Fixes for Tuscany SCA Java 0.91 RC4?

[Jean-Sebastien Delfino <js...@apache.org>]

ant elder wrote:
> On 7/18/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>
> <snip>
> ...
>>
>> and other bindings that don't support references) break
>> when initializing self references
>
>
> Isn't this a more general problem with the way self references are handle
> right now? What was the fix that was done for this, I can't see any 
> commit
> comments mentioning it?
>
>   ...ant
>

Raymond may be able to give more details, but it looks like it was a 
change in CompositeActivator in the commit for TUSCANY-1435.

We currently create self references for all services of a component to 
allow the component to get a self reference (see 
ComponentContext.createSelfReference) and for top level components this 
also allows SCADomain.locateService to work off that reference.

Some bindings do not support references, so we need to be able to detect 
that (I guess they don't have a ReferenceBindingProvider) and for 
services configured with these bindings createSelfReference should throw 
an exception.

I think we could improve the code to detect that a binding does not 
handle references early on, instead of just catching an exception like 
we do now. Any other concrete proposal to improve the handling of self 
references?

-- 
Jean-Sebastien


---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org