Bug 29213 - XML Namespace URI required when making WCF request with JSON
Summary: XML Namespace URI required when making WCF request with JSON
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: WCF assemblies ()
Version: 3.12.0
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2015-04-17 16:43 UTC by edwinguy
Modified: 2017-09-06 16:55 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 29213 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description edwinguy 2015-04-17 16:43:47 UTC
The main problem I'm running up against is that my WCF client isn't able to serialize its request to JSON properly. From the stack trace (see pastebin link below), it looks like the message is being converted to XML first, then to JSON.

This seems a bit odd since WebMessageEncoder.WriteMessage(Message, Stream) should be able to handle the JSON encoding directly if GetContentFormat(Message) returned the right WebContentFormat.

Let me know if it's worth building a real-working project for this.

Here's the relevant snippets of code (may have syntax errors):

Here's the stack trace: