Mike Edwards wrote:
<snip>
I think that there are changes required in the following areas:
...
3) The bindings need to be involved. You rightly say that we need to
mark the bindings as "providing" the asyncInvocation intent.
...
Yours, Mike.
OK,
I've taken the first step on this one.
binding.sca, binding.jms and binding.jms all now have @mayProvide="sca:asyncInvocation" in their
definitions.xml files.
This enables the EPR to EP mapping to get past the Intent/Policy mapping step when running
JCA_7003_TestCase.
I know that at the moment none of the bindings will actually do the async invocation correctly, but
the approach Kelvin & myself are taking on this is to use JCA_7003_TestCase as the driver for the
development of the changes necessary. The principle is to simply fix each problem encountered in
the execution of this testcase one by one until everything works. Some steps will be simple, other
ones will be complex, but this is "test driven development" ! ;-)
The next step is to fix up the interface mapping between the (client) synchronous version of the
service interface and the (server) async version, so that these visibly different (Java) interfaces
are treated as being compatible.
Yours, Mike.
