No you don't, you just need to confugure the client to 'use a separate listener' and the runtime will do the rest.
See the EchoBlockingDualClient sample described at [1] David [1] http://ws.apache.org/axis2/1_1_1/userguide-samples.html On 05/03/07, Jim Alateras <[EMAIL PROTECTED]> wrote:
Callner, David A. wrote: > No problem > are there any examples of such a scenario? How does this work? Do I need to specify something in the binding section indicating that the response will be sent asynchronously and in a separate connection to that of the request. cheers </jima> > -----Original Message----- > From: Jim Alateras [mailto:[EMAIL PROTECTED] > Sent: Monday, March 05, 2007 1:41 PM > To: [email protected] > Subject: Re: WS-Addressing SOAP binding question > > David Illsley wrote: >> Hi, >> What do you mean by support? > Hi David. If i have a request reply operation that is bound to > SOAP/HTTP > and I supply a non-anonymous URI for the ReplyTo address can I get > behaviour specified in 5.2.1 below. > > Will the generated stubs and skeletons work? > > cheers > </jima> >> David >> >> On 05/03/07, Jim Alateras <[EMAIL PROTECTED]> wrote: >>> I was wondering whether axis2 supports the following WS-Addressing > SOAP >>> Binding requirements from >>> (http://www.w3.org/TR/2006/REC-ws-addr-soap-20060509/) >>> >>> >>> >>> 5.2 Use of Non-Anonymous Addresses in SOAP Response Endpoints >>> 5.2.1 SOAP 1.1/HTTP >>> >>> When "http://www.w3.org/2005/08/addressing/anonymous"; is not > specified >>> for the response endpoint, then the message SHOULD be part of a > binding >>> that supports not returning a SOAP envelope in the HTTP response > (e.g. >>> see [SOAP 1.1 Request Optional Response HTTP Binding]). Any response >>> message SHOULD be sent using a separate connection and using the > address >>> value specified by response endpoint. Note that other specifications > MAY >>> define special URIs that have other behaviors (similar to the > anonymous >>> URI). >>> 5.2.2 SOAP 1.2 >>> >>> When "http://www.w3.org/2005/08/addressing/anonymous"; is not > specified >>> for the response endpoint, then any response SHOULD NOT be the >>> http://www.w3.org/2003/05/soap/mep/OutboundMessage property of the > same >>> instance of the SOAP request-response MEP [SOAP 1.2 Adjuncts]. For >>> instance, a SOAP 1.2 HTTP binding that supports a one-way MEP could > put >>> the reply message in a separate one-way MEP and a separate HTTP > request. >>> As in SOAP 1.1/HTTP, note that other specifications MAY define > special >>> URIs that have other behaviors (similar to the anonymous URI) >>> >>> cheers >>> </jima> >>> >>> > --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- David Illsley - IBM Web Services Development --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
