I'm just starting to look at JCA_7003 through 6 so wanted to kick off a thread about how to get async invocation working over the default binding (it only operates over binding.ws at the moment). I've started with 7003 which happens to be the interesting case of a synch reference and an asynch service.
What I'm first trying to work out is how the async callback Endpoint is intended to be generated. The code to do this kind of thing is in the AsynchJDKInvocationHandler. This is injected by the JDKProxyFactory if it detects an async reference. So it won't be injected in this case as only the service is async. If it were injected if would, in this case, look to see if the target is asynch. However is does this before the bind has resolved the target so an issue there as well. I hacked both of these locally and am looking at the next issue. We do have the option of course to special case the local default binding so that the callback reference is not required but It would be useful to understand the full flow before optimizing. Any insight appreciated. Regards Simon -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
