W3C home > Mailing lists > Public > www-ws-desc@w3.org > May 2006

RE: Interchange result update.

From: Lawrence Mandel <lmandel@ca.ibm.com>
Date: Fri, 26 May 2006 15:59:58 -0400
To: www-ws-desc@w3.org
Message-ID: <OFD95295A2.B486BCB5-ON8525717A.006D60C9-8525717A.006DDC7C@ca.ibm.com>
I've opened the following Woden Jira reports for the problems Jonathan 
reported in his post below.

2) http://issues.apache.org/jira/browse/WODEN-16
3) http://issues.apache.org/jira/browse/WODEN-17
4) http://issues.apache.org/jira/browse/WODEN-18

Lawrence Mandel

Software Developer
IBM Rational Software
Phone: 905 - 413 - 3814   Fax: 905 - 413 - 4920

"Jonathan Marsh" <jmarsh@microsoft.com> 
05/25/2006 09:42 AM

Lawrence Mandel/Toronto/IBM@IBMCA

RE: Interchange result update.

Not really ;-)  But I?d appreciate it if you would!

From: Lawrence Mandel [mailto:lmandel@ca.ibm.com] 
Sent: Wednesday, May 24, 2006 9:42 PM
To: Jonathan Marsh
Subject: Re: Interchange result update.

Hi Jonathan, 

Thanks for the summary. It's good to see others testing Woden and 
providing feedback. Care to open Jira reports [1] for these problems? 

[1] http://incubator.apache.org/woden/issue_tracking.html 

Lawrence Mandel

"Jonathan Marsh" <jmarsh@microsoft.com> 
Sent by: www-ws-desc-request@w3.org 
05/24/2006 03:31 PM 

Interchange result update.


I checked in a new version with the new Woden results, my stylesheet 
updated to support the soap binding extensions and the safety extension. 
(doesn?t yet do the rpc extension). 
Naturally, when there was a question I chose my implementation as the 
baseline ;-). 
Woden results appear to me to suffer from several problems: 
1)       {safety} property is often missing.  I sent an issue on whether 
this is a valid interpretation of the spec. 
2)       When message content model is #none, Woden emits an invalid 
<elementDeclaration ref=?id-null?/> reference. 
3)       When a binding doesn?t specify an interface, Wodwn emits an 
invalid <interface ref=?id-null?/> reference. 
4)       Woden often omits {soap underlying protocol}, though this is a 
REQUIRED property in the spec. 
5)       Some element declaration components still appear to be missing. 

 [  Jonathan Marsh  ][  jmarsh@microsoft.com  ][  
http://spaces.msn.com/auburnmarshes  ]

Received on Friday, 26 May 2006 20:00:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:06:58 UTC