Hi You don't need to change the transport. You should set "setUseSeparateListener()" as in the Axis2 case.
In my experience .NET does not behave properly - you need to explicitly code a .NET service to behave in what they call "Dupklex" mode if you want to have true non-blocking and two async HTTP connections. Paul On 9/23/07, zhrb <[EMAIL PROTECTED]> wrote: > > Hello, > > I am now using axis2 accessing .net web service following samples of > "EchoNonBlockingDualClient".The userguide just mentions the condition of > both web service and client are based on axis2.But if my web service is .net > web service,how should I use Axis2 client > to access in the "EchoNonBlockingDualClient" way?How should I change this > line below: > > options.setTransportInProtocol(Constants.TRANSPORT_HTTP); > > Waiting for your answer!Thanks! > > > -Zhang > > > > > ________________________________ > 使用新一代 Hotmail，更强大、更安全、更多存储空间！ 立刻体验！ -- Paul Fremantle Co-Founder and VP of Technical Sales, WSO2 OASIS WS-RX TC Co-chair blog: http://pzf.fremantle.org [EMAIL PROTECTED] "Oxygenating the Web Service Platform", www.wso2.com
