I committed changes based on this submission to provide one-way support on the client. I tested the changes against a .NET service.
Scott Nichol ----- Original Message ----- From: "Pavel Ausianik" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, November 16, 2002 7:05 AM Subject: RE: Apache SOAP and request only Web Services. > Hello > > I prepared short patch for the client side only - but didn't had possibility > to test it. > > Pavel > > > -----Original Message----- > > From: Scott Nichol [mailto:[EMAIL PROTECTED]] > > Sent: Saturday, November 09, 2002 11:21 PM > > To: [EMAIL PROTECTED] > > Subject: Re: Apache SOAP and request only Web Services. > > > > > > It is not a lot of code to change to support this on both the > > client and > > the server, and for that matter, for both messaging and RPC. However, > > no one working on Apache SOAP has chosen to do this with the limited > > time they spend on the project. > > > > Scott Nichol > > > > ----- Original Message ----- > > From: "Ashutosh Arora" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Cc: <[EMAIL PROTECTED]> > > Sent: Saturday, November 09, 2002 2:55 PM > > Subject: Re: Apache SOAP and request only Web Services. > > > > > > > > > > For client side is it possible to provide this support in > > Apache SOAP. > > > Assuming I do not want to go for rpc invocation. I create my soap > > message > > > using Apache SOAP. I want to invoke a Web Service using the messge > > oriented > > > technique given in the Apache SOAP messaging sample. > > > > > > This Web Service is a SOAP/HTTP request only Web Service. > > Based on my > > > understanding with existing Web Services implementations, a request > > only > > > SOAP/HTTP Web Service will respond back with HTTP STatus > > code of "202 > > > Accepted". If we can provide some support in > > > org.apache.soap.messaging.Message class, so that if it sees HTTP > > status > > > code of 202 accepted it will not try to create SOAPEnvelope. I think > > this > > > support will be very helpful for people using Apache SOAP > > client-only > > API, > > > in consuming request only web services. > > > > > > Just a suggestion. > > > Thanks > > > -Ashutosh > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > |---------+-----------------------------> > > > | | Scott Nichol | > > > | | <snicholnews@scott| > > > | | nichol.com> | > > > | | | > > > | | 11/07/2002 08:46 | > > > | | PM | > > > | | Please respond to | > > > | | soap-dev | > > > | | | > > > |---------+-----------------------------> > > > > > >------------------------------------------------------------- > > ---------- > > -------------------------------------------------------------- > > --------| > > > | > > | > > > | To: [EMAIL PROTECTED] > > | > > > | cc: > > | > > > | Subject: Re: Apache SOAP and request only Web Services. > > | > > > | > > | > > > | > > | > > > > > >------------------------------------------------------------- > > ---------- > > -------------------------------------------------------------- > > --------| > > > > > > > > > > > > Apache SOAP does not currently implement something equivalent the > > > one-way ports specified in WSDL > > > (http://www.w3.org/TR/wsdl.html#_one-way). I am not certain what > > > specification says how to implement this on HTTP. Microsoft has the > > > server respond with an empty (no entity) HTTP response with > > some magic > > > status like "216 Received" after the SOAP request is validated, but > > > before the service is actually executed. I would like to > > have this in > > > Apache SOAP, but have not yet had time to add it. > > > > > > The current Apache SOAP code (1) always executes the service before > > > transmitting an HTTP response and (2) always transmits a > > SOAP envelope > > > as the HTTP entity. The closest thing to one-way operations is any > > > service with a void return type. > > > > > > Scott Nichol > > > > > > ----- Original Message ----- > > > From: "Ashutosh Arora" <[EMAIL PROTECTED]> > > > To: <[EMAIL PROTECTED]> > > > Sent: Thursday, November 07, 2002 5:20 PM > > > Subject: Apache SOAP and request only Web Services. > > > > > > > > > > Hi, > > > > > > > > Is it possible to invoke request only Web Services using Apache > > SOAP? > > > I > > > > want to use SOAP/HTTP to invoke a request only Web > > SErvice. Is there > > > any > > > > way I can leverage Apache SOAP to do that? Is there any > > sample code > > > that I > > > > can refer to? > > > > Any help will be greatly appreciated. > > > > > > > > Thanks > > > > -Ashutosh > > > > > > > > > > > > > > > > > > > > -- > > > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > > -- > > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > > > > > > > > > > -- > > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > For additional commands, e-mail: > > <mailto:[EMAIL PROTECTED]> > > > > > > > > > > > > -- > > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > ------------------------------------------------------------------------ -------- > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
