[
https://issues.apache.org/jira/browse/TUSCANY-3659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws updated TUSCANY-3659:
--------------------------------
Attachment: 3659-1.patch
Local changes to turn on asyn operation for the default binding when the client
is sync but the server is async. Attaching as patch so we can discuss. Several
issues with this including:
It's not optimized for the local binding.sca case
AsyncJDKInvocationHandler is on all the time
WS_MESSAGE_ID has bled into generic code
synch calls still have to handle async fault which results in
UndeclaredTrhowableException rather than real business fault. This will be a
problem for sync calls through a reference interface marked as async also.
> Get asyn support working with binding.sca
> -----------------------------------------
>
> Key: TUSCANY-3659
> URL: https://issues.apache.org/jira/browse/TUSCANY-3659
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Core Runtime, OASIS Compliance - TUSCANY
> Affects Versions: Java-SCA-2.0-M5
> Environment: all
> Reporter: Simon Laws
> Assignee: Simon Laws
> Attachments: 3659-1.patch
>
>
> otests JCA_7003/4/5/6 test async operation with the default SCA binding. SCA
> binding doesn't support asynch at the moment.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
