Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 77665 invoked from network); 19 Mar 2005 04:44:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 19 Mar 2005 04:44:36 -0000 Received: (qmail 37000 invoked by uid 500); 18 Mar 2005 19:32:31 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 36986 invoked by uid 500); 18 Mar 2005 19:32:31 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 36972 invoked by uid 99); 18 Mar 2005 19:32:31 -0000 X-ASF-Spam-Status: No, hits=0.4 required=10.0 tests=DNS_FROM_RFC_ABUSE,RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of ephemeris.lappis@gmail.com designates 64.233.170.206 as permitted sender) Received: from rproxy.gmail.com (HELO rproxy.gmail.com) (64.233.170.206) by apache.org (qpsmtpd/0.28) with ESMTP; Fri, 18 Mar 2005 11:32:30 -0800 Received: by rproxy.gmail.com with SMTP id g11so271178rne for ; Fri, 18 Mar 2005 11:32:28 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:message-id:mime-version:content-type:content-transfer-encoding:x-priority:x-msmail-priority:x-mailer:in-reply-to:importance:x-mimeole; b=FJups9CjOZNi02cSre+Sz9sk4DZkIg+jtFJKtM7zDaMEruaoYH5UeC+EZPawGY0xH2qr2x1BhhnokcIcS0UbdL2igKCr1DDIWrqgujXH7xG1RaVxbGm3RKi6FVuIfYbhZFZKbzh52UmHBDsGQ6kHsjY8cmclqzlteWjsrcUvG6Q= Received: by 10.38.207.18 with SMTP id e18mr2523930rng; Fri, 18 Mar 2005 11:32:28 -0800 (PST) Received: from alhambra ([83.157.123.148]) by mx.gmail.com with ESMTP id m37sm486303rnd.2005.03.18.11.32.27; Fri, 18 Mar 2005 11:32:28 -0800 (PST) From: "Ephemeris Lappis" To: Subject: RE: 'response' to one-way operation Date: Fri, 18 Mar 2005 20:31:50 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <423B2A7D.9090006@aesgi.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Think that the http protocol is just a transport binding for your service. In the future, another binding should be selected : for the one-way call, an asynchronous protocol could be a good candidate. Your client code should not be aware of this technical detail, the same way your client logic should not depend on the soap choice... I suppose that if the client soap stack doesn't throw back an error, your one way request has been successfully processed, and it's just what you need to known... Onece more, it's just my opinion ! -- Philippe Maseres >>> -----Message d'origine----- >>> De : Gregory G Carter [mailto:gcarter@aesgi.com] >>> Envoye : vendredi 18 mars 2005 20:23 >>> A : axis-user@ws.apache.org >>> Objet : Re: 'response' to one-way operation >>> >>> >>> I furthermore... >>> >>> Is there a map of the response codes you get back from the http >>> transport session vs the exceptions you get for a soap request. >>> >>> I think I could probably answer that one myself by cracking open the >>> source code...but >>> >>> I am lazy at the moment. >>> >>> -gc >>> >>> Anne Thomas Manes wrote: >>> >>> >HTTP is a request/response protocol, so a response is always returned >>> >to the client -- HTTP 200 OK. No SOAP response is returned, though. >>> > >>> > >>> >On Fri, 18 Mar 2005 09:36:17 -0800, Jeff Greif >>> > wrote: >>> > >>> > >>> >>When a one-way operation is invoked via SOAP over HTTP, is >>> there an HTTP >>> >>response to the client, or is the connection just closed by >>> the server? If >>> >>there is some sort of response, what is supposed to appear on >>> the wire back >>> >>to the client? >>> >> >>> >>Jeff >>> >> >>> >> >>> >> >>> >> >>> > >>> >. >>> > >>> > >>> > >>>