Bugzilla – Bug 434892
wsdl crashes with muine's amazon web service
Last modified: 2008-10-30 19:45:20 UTC
The file hasn't changed for years, it worked in mono 1.9.1 and fails in mono 2.0 on Mandriva Cooker: $ wsdl http://svn.gnome.org/svn/muine/trunk/src/AmazonSearchService.wsdl Web Services Description Language Utility Mono Framework v2.0.50727.42 Error: Key duplication when adding: System.Web.Services.Description.MessagePart Stack: at System.Collections.Hashtable.PutImpl (System.Object key, System.Object value, Boolean overwrite) [0x00000] at System.Collections.Hashtable.Add (System.Object key, System.Object value) [0x00000] at System.Web.Services.Description.BasicProfileChecker.Check (System.Web.Services.Description.ConformanceCheckContext ctx, System.Web.Services.Description.Binding value) [0x00000] at System.Web.Services.Description.WebServicesInteroperability.Check (System.Web.Services.Description.ConformanceCheckContext ctx, System.Web.Services.Description.ConformanceChecker checker, System.Web.Services.Description.Binding b) [0x00000] at System.Web.Services.Description.WebServicesInteroperability.Check (System.Web.Services.Description.ConformanceCheckContext ctx, System.Web.Services.Description.ConformanceChecker checker, System.Web.Services.Description.ServiceDescription sd) [0x00000] at System.Web.Services.Description.WebServicesInteroperability.Check (WsiProfiles claims, System.Web.Services.Description.ConformanceCheckContext ctx, IEnumerable documents) [0x00000] at System.Web.Services.Description.WebServicesInteroperability.CheckConformance (WsiProfiles claims, System.Web.Services.Description.WebReference webReference, System.Web.Services.Description.BasicProfileViolationCollection violations) [0x00000] at Mono.WebServices.Driver.GenerateCode (System.Web.Services.Description.WebReferenceCollection references, System.CodeDom.CodeCompileUnit codeUnit) [0x00000] at Mono.WebServices.Driver.Run (System.String[] args) [0x00000]
Any pointers on this ? I couldn't understand what's wrong.
It still fails in Mono 2.0.1.
(I have never exposed this email.)
Fixed in svn (r117243).
Atsushi fixed it