W3C home > Mailing lists > Public > public-ws-addressing-tests@w3.org > March 2006

Re: WSO2 -> Axis issues (PLEASE READ, SPEC/TEST ISSUES)

From: Davanum Srinivas <dims@wso2.com>
Date: Wed, 15 Mar 2006 11:11:28 -0500
Message-ID: <44183CB0.2030007@wso2.com>
To: Glen Daniels <gdaniels@sonicsoftware.com>
CC: public-ws-addressing-tests@w3.org, dims@apache.org

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul,
Please pick up the latest wso2-axis.xml from the usual location.

Glen,
Latest update should clear up the wso2->axis failures.

thanks,
- -- dims

Glen Daniels wrote:
> 
>> Aside from the "duplicate FaultTo" tests (1142,1242), I 
> 
> I actually meant aside from the "duplicate ReplyTo" tests (1141,1241).
> When there's a duplicate FaultTo, that means the [fault endpoint]
> property can't be resolved, and any faults will default to going to the
> [reply endpoint], which in this case is "none".  So I think we're OK on
> 1142/1242 (if WSO2 stops sending "none"), and now that the endpoint has
> been refreshed to fix the issue we clarified on Monday (i.e. don't
> generate a property value if the headers are wrong for that property),
> we should be OK on 1141/1241.
> 
>> believe Axis is behaving entirely reasonably according to the 
>> spec - we are generating a fault (for instance, "duplicate To 
>> header") and then sending it to the FaultTo address, which 
>> defaults to the ReplyTo address if no <FaultTo> is present.  
> 
> Thanks,
> --Glen
> 
> 


- --
Davanum Srinivas (dims@wso2.com)
VP/Engg, WSO2 (http://wso2.com)
Yahoo IM: dims Cell/Mobile: +1 (508) 415 7509
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)

iD8DBQFEGDywgNg6eWEDv1kRAktaAKCA8tumPrqbIXddVNDI0e/dgZfmPgCfTjDw
TA67xj4o/Qv8+avm7HkjbBQ=
=ZgLB
-----END PGP SIGNATURE-----
Received on Wednesday, 15 March 2006 16:14:31 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:54:42 UTC