I'm looking at the current infrastructure that supports asynchronous invocation. We pass the OASIS tests but there are a number of improvements I think we could/should make. I've raised TUSCANY-3783 [1] with sub-tasks to track. The most difficult issue I see at the moment is TUSCANY-3786 [2] which is the way that the Java and infrastructure parts are a bit intermingled. This makes it tricky to re-use the infrastructure for other implementation types. To start looking at this I've made a copy of samples\extending-tuscany\implementation-sample at unreleased\samples\implementation-sample-async. I plan to start this by trying to apply the async infrastructure to this new implementation type to see what doesn't work.
I've also created a wiki page [3] to capture any thoughts from the ML and included a diagram of how I think it looks now. Any thoughts and/or help are most welcome. [1] https://issues.apache.org/jira/browse/TUSCANY-3783 [2] https://issues.apache.org/jira/browse/TUSCANY-3786 [3] https://cwiki.apache.org/confluence/display/TUSCANYWIKI/Asynch+Infrastructure Regards Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
