[ 
https://issues.apache.org/jira/browse/TUSCANY-3932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179567#comment-13179567
 ] 

Simon Laws commented on TUSCANY-3932:
-------------------------------------

I've been looking at this an I also note that there is code in the 
CallbackServiceReference that resets the binding on the original callback 
endpoint reference rather than the cloned version which doesn't sound right. 
Also after the clone the binding provider isn't reset so in effect the binding 
provider, and associated wires, are shared between all callback references for 
a particular component. I suspect that this will cause problems for concurrent 
requests to the component. 
                
> Callbacks don't work in the distributed domain
> ----------------------------------------------
>
>                 Key: TUSCANY-3932
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-3932
>             Project: Tuscany
>          Issue Type: Bug
>          Components: SCA Java Runtime
>    Affects Versions: Java-SCA-2.0-Beta3
>         Environment: All
>            Reporter: Simon Laws
>            Assignee: Simon Laws
>             Fix For: Java-SCA-2.0
>
>
> The callback wire calculation currently requires knowledge of the service 
> runtime. This will not be available in the distributed case where the 
> Endpoint matched by and retrieved from the registry will not have a built 
> runtime behind it. We need to refactor this based on the configuration 
> available in the SCDL written to represent a remote Endpoint.
> Of particular interest is callback bindings that are generated vs callback 
> bindings that are specified by the user. If a user specifies a binding this 
> should automatically be available in the reference node as it will be written 
> be default when the Endpoint is written out. Automatically generated callback 
> bindings, usually generated to match the forward binding, won't be in that 
> list and won't get written out so we need to address that. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to