I've been playing around with the new CallableReference support and thought I would add a test to itest-callablereference to repeat all the tests but using the remote SCA Binding in some cases.
Can I assume that CallableReference serialization is not done yet. I put a test in but it fails as the infrastructure doesn't know how to deserialize a callable reference. I looked a little closer and found - The CallableReference doesn't have a no parameter constructor. Also can someone explain how the infrastructure knows it has to fluff up a CallableReferenceImpl if it finds an operation taking a CallableReference interface? It doesn't know at the moment and tries to instantiate the interface but how is it intended that it knows? - Only a small amount of data is written out when you serialize it in the first place. This was the SOAP message that was produced POST /BComponent HTTP/1.1 Content-Type: text/xml; charset=UTF-8 SOAPAction: "urn:fooC" User-Agent: Axis2 Host: localhost:8086 Content-Length: 375 <?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv=" http://schemas.xmlsoap.org/soap/envelope/";><soape nv:Body><_ns_:fooC xmlns:_ns_=" http://callableref.itest.sca.tuscany.apache.org/xsd";><param0 xmlns=" http://callableref.it est.sca.tuscany.apache.org/xsd"><conversationID xmlns="" /><callback xmlns="" /></param0></_ns_:fooC></soapenv:Body></so apenv:Envelope> Regards Simon
