Ok, so as I understand it, this currently works today i.e. without polling, provided that the transportIn etc is setup.
I agree that Sandesha needs to setup an async listener for an addressable acksTo. However, is it necessarily right that the client or jaxWS layer should know that, by setting an acksTo, it also has to set up a transportInProtocol, in order for this async listener to be set up? It seems to me that some implementation detail of sandesha is that an async listener is used to receive response messages during an addressable synchronous flow. It seems therefore that it would be good to shield the jaxWS layer from this implementationd detail. What would be the effect of using transportOut details to setup the transportIn in the case of one not having been set?
OK. This seems to be a valid requirement. I'll do this change. Thaks for pointing it out
Done.
Chamikara
