RE: echo:EmptyEchoString -- was RE: Misc comments

OK, I'll track this as an issue:

http://www.w3.org/2002/ws/addr/testsuite/issues/#test12

Paul


-----Original Message-----
From: Arun Gupta [mailto:Arun.Gupta@Sun.COM]
Sent: Thu 12/22/2005 8:49 AM
To: Downey,P,Paul,CXMA C
Cc: public-ws-addressing-tests@w3.org
Subject: Re: echo:EmptyEchoString -- was RE: Misc comments
 
Agreed that this error is caused by the application but this is imposing 
another requirement on the toolkits to be able to support custom 
faultcodes from within their application. I think that is out-of-scope 
for WS-Addressing and it should be a standard code (say client or server).

-Arun

paul.downey@bt.com wrote:
> Arun
> 
> 
>>4). What functionality of WS-Addressing are we testing by setting the 
>>fault code to "echo:EmptyEchoString" ? I think it should one of the 
>>standard faultcodes, probably env:Client.
> 
> 
> This approach stems from the Microsoft submitted scenarios:
> 
> http://www.w3.org/2002/ws/addr/testsuite/submissions/Microsoft/WS_Addressing_Scenarios.htm
> 
> The idea being to have a simple method of triggering a
> fault and I'd anticipate this being thrown by the echo 
> 'method' in application space rather than by infrastructure.
> 
> I'd prefer to have separate tests for the WS-Addressing specific 
> faults.
> 
> Paul

-- 
got Web Services ?
Download Java Web Services Developer Pack from
http://java.sun.com/webservices

Received on Thursday, 22 December 2005 10:47:24 UTC