On 7/18/07, Raymond Feng <[EMAIL PROTECTED]> wrote:
Hi,
Assuming we have the following declaration: reference r1 is wired to
service
s1.
<reference name="r1">
<interface.wsdl interface="http://ns1#wsdl.interface(Service1)"
callbackInterface="http://ns1#wsdl.interface(Service1Callback)"/>
<binding.ws .../>
<callback>
<binding.ws .../>
</callback>
</reference>
<service name="s1">
<interface.wsdl interface="http://ns1#wsdl.interface(Service1)"
callbackInterface="http://ns1#wsdl.interface(Service1Callback)"/>
<binding.ws .../>
<callback>
<binding.ws .../>
</callback>
</reference>
Then the callback path seems to be following: s1 (binding.ws) ---> r1
(binding.ws). Is this like another web service call? or is it really that
the s1 provides asynchronous response to the web service layer and the web
service client is making a callback?
For the forward call, r1 --> ws client ......(soap/http) .....ws
service -->s1. Which path should be used for the callback?
1) s1--> ws client ......(soap/http) .....ws service -->r1 (another
regular
ws call)
or
2) s1--(ws-callback)--> ws server ...(soap/http) ... ws
client --(ws-callback)-->r1 (over ws callback MEP)
Thanks,
Raymond
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Well 1) would be useful if the callback occurs outside of the context of
the original call or if the callback doesn't happen for a really long time,
i.e. long enough for connection timeouts. Downside, I guess, is to do the
plumbing to host the callback.
Simon
