I am using dual channel. I do not want to stop listener itself as it is being reused by multiple sessions, but I am trying to figure out how to invalidate a particular session on the client side.
According to http://ws.apache.org/axis2/1_4_1/jaxws-guide.html - Using an asynchronous message exchange: "For asynchronous exchanges, there is no timeout that is sent to notify the client to stop listening for a response. To force the client to stop waiting for a response, issue a Response.cancel() method on the object returned from a polling invocation or a Future.cancel() method on the object returned from a callback invocation." So if I understand it correctly, once a client receives asynchronous response from a service through a separate listener, it will correlate it to a waiting thread through a message id and execute a callback. Per documentation, it appears that I am responsible to notify waiting thread if I am no longer interested in a response and to stop waiting. However generated stubs have void methods instead of returning Future<?> as stated in the documentation. Am I missing something here? -Dmitriy On Sat, Oct 4, 2008 at 12:56 AM, keith chapman <[EMAIL PROTECTED]>wrote: > Your question is not too clear. When you say "I am now trying to notify a > client to stop listening in case a timeout is necessary" do you mean you > want to stop the listener on the client? Are you using dual channel > invocation or single channel? > > Thanks, > Keith. > > > On Sat, Oct 4, 2008 at 2:51 AM, Dmitriy Frolov <[EMAIL PROTECTED]>wrote: > >> All, >> I was able to successfully create an asynchronous service along with a >> client using asynchronous message exchange. >> >> I am now trying to notify a client to stop listening in case a timeout is >> necessary. However generated stubs have void methods and do not return >> Future<?> handle. I tried to follow documentation with no luck. I am using >> asyncOnly option for wsdl2java and have following in my wsdl: >> >> <jaxws:bindings xmlns:jaxws="http://java.sun.com/xml/ns/jaxws";> >> <jaxws:enableAsyncMapping>true</jaxws:enableAsyncMapping> >> </jaxws:bindings> >> >> Axis version 1.4.1 >> >> Did anyone had similar issues or know what I might be missing here? >> >> -Dmitriy >> > > > > -- > Keith Chapman > Senior Software Engineer > WSO2 Inc. > Oxygenating the Web Service Platform. > http://wso2.org/ > > blog: http://www.keith-chapman.org >
