te that to java2wsdl,
and suspect that I'll have to manually edit the generated wsdl.
From: Guy Rixon <[EMAIL PROTECTED]>
Reply-To: axis-user@ws.apache.org
To: axis-user@ws.apache.org
Subject: Re: Explicit response required from WS methods?
Date: Wed, 31 Aug 2005 17:15:26 +0100 (BST)
H
n anything (even though
it might be advisable to do so, the question here is one of necessity).
From: "Chris Nappin" <[EMAIL PROTECTED]>
Reply-To: axis-user@ws.apache.org
To:
Subject: RE: Explicit response required from WS methods?
Date: Wed, 31 Aug 2005 16:48:14 +0100
Ha
Hi,
void is fine, and saves a little parsing on the return. If it works, then the
service returns an HTTP 200 with a SOAP body that doesn't need deserializing;
the client stub returns quietly. If it goes wrong, then the client stub chucks
an Exception in which the detail states the HTTP status-cod
on exx) {throw new SOAPException(exc); }}>From: Rogério Luz <
[EMAIL PROTECTED]>>Reply-To: axis-user@ws.apache.org>To: axis-user@ws.apache.org>Subject: Re: Explicit response required from WS methods?
>Date: Wed, 31 Aug 2005 12:54:09 -0300>>Depends on what service.delete
org
To: axis-user@ws.apache.org
Subject: Re: Explicit response required from WS methods?
Date: Wed, 31 Aug 2005 12:54:09 -0300
Depends on what service.deleteEmployee() method do. If you have a try/catch
there and an Exception is thrown you'll never know if your delete really
happaned. Certainl
Nice link, thanks a lot Chris.
From: "Chris Nappin" <[EMAIL PROTECTED]>
Reply-To: axis-user@ws.apache.org
To:
Subject: RE: Explicit response required from WS methods?
Date: Wed, 31 Aug 2005 16:48:14 +0100
Have a look at the various scenarios in the WS-I Usage Scenarios sp
axis-user@ws.apache.org>Subject: Re: Explicit response required from WS methods?>Date: Wed, 31 Aug 2005 12:43:41 -0300>>I think it would be a good practice return at least a boolean to ensure
>your>deleteEmployee method really deleted an employee.>>On 8/31/05, Jarmo Doc <[E
ser@ws.apache.org
Subject: Explicit response required from WS methods?
Let's say that I have a WS method like so:
deleteEmployee(int empid) throws SOAPException
{
}
Is it sensible for this method to have a void return type or should it
always return something, for example the
rg
To: axis-user@ws.apache.org
Subject: Re: Explicit response required from WS methods?
Date: Wed, 31 Aug 2005 12:43:41 -0300
I think it would be a good practice return at least a boolean to ensure
your
deleteEmployee method really deleted an employee.
On 8/31/05, Jarmo Doc <[EMAIL PROTECTED]>
I think it would be a good practice return at least a boolean to ensure
your deleteEmployee method really deleted an employee.On 8/31/05, Jarmo Doc <[EMAIL PROTECTED]> wrote:
Let's say that I have a WS method like so: deleteEmployee(int empid) throws SOAPException
{ }Is it sensible for this me
Let's say that I have a WS method like so:
deleteEmployee(int empid) throws SOAPException
{
}
Is it sensible for this method to have a void return type or should it
always return something, for example the empid just deleted (for client
correlation purposes, amongst other things)?
I ask b
11 matches
Mail list logo
