[jira] Commented: (TUSCANY-3786) In the async programming model provide a clear separate between the Java specific bits and the infrastructure bits so it can be used by other implementation types

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

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

Simon Laws commented on TUSCANY-3786:
-------------------------------------

The first part I've looked at is the AsyncJDKInvocation handler. Firsly it's a little odd that these handlers are in Core. Something to do with SCA clients? But related to async specifically this includes all the code for suppoting the various Java async interfaces (sync/poll/callback) and th generic underlying code for dispatching the asyn which could be part of the generate runtime (EndPointReference?)

> In the async programming model provide a clear separate between the Java specific bits and the infrastructure bits so it can be used by other implementation types
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: TUSCANY-3786
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-3786
>             Project: Tuscany
>          Issue Type: Sub-task
>    Affects Versions: Java-SCA-2.0-Beta1
>         Environment: all
>            Reporter: Simon Laws
>             Fix For: Java-SCA-2.0
>
>
> The current async programming model is Java centric and some of this bleeds over into the infrastrcture. I would be good if the programming model were applicable to other implementation types such as BPEL. 

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