[Mono-bugs] [Bug 638520] New: Exception calling web service with wcf proxy from ms silverlight
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Fri Sep 10 10:45:34 EDT 2010
https://bugzilla.novell.com/show_bug.cgi?id=638520
https://bugzilla.novell.com/show_bug.cgi?id=638520#c0
Summary: Exception calling web service with wcf proxy from ms
silverlight
Classification: Mono
Product: MonoTouch
Version: SVN
Platform: Macintosh
OS/Version: Mac OS X 10.6
Status: NEW
Severity: Major
Priority: P5 - None
Component: Class Libraries
AssignedTo: gnorton at novell.com
ReportedBy: mike.bluestein at gmail.com
QAContact: mono-bugs at lists.ximian.com
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_4; en-US)
AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.55 Safari/534.3
Generating a proxy either directly on the command line on windows using
slsvcutil or via add service reference in a silverlight project and then using
the resulting proxy code in monotouch results in a runtime argument exception
using the soap based version of the bing web service.
Related perhaps -> in the generated proxy code that works in silverlight, I
needed to comment out the attribute that uses "SupportsFaults" in order to get
it to compile in monotouch (see line 22 in the Reference.cs class in the
attached test case).
Reproducible: Always
Steps to Reproduce:
1.Create a proxy to the bing soap service on windows using slsvcutil
2.Copy the proxy into a monotouch project
3.Call the web service
Actual Results:
web service returning from async call with results
Expected Results:
Exception in async operation: System.ArgumentException Non-empty prefix must be
mapped to non-empty namespace URI.
I have attached 2 test cases, a monotouch project that results in the exception
and a silverlight project using the same proxy class (vs.net) that writes the
Bing service call search results to the debug console.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the mono-bugs
mailing list