Bug 3218 - WebServices 2.0: System.Web.Services.Protocols.SoapHttpClientProtocol.GetWriterForMessage () is never called
Summary: WebServices 2.0: System.Web.Services.Protocols.SoapHttpClientProtocol.GetWrit...
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.Web.Services ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2012-02-03 07:26 UTC by René Ruppert
Modified: 2015-05-20 06:44 UTC (History)
6 users (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 3218 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:

Comment 2 Rolf Bjarne Kvinge [MSFT] 2012-02-07 20:12:41 UTC
This turned out a quite much harder to fix than I thought at first sight.

The easy part is to add the support for GetWriterForMessage - but then it turns out that I have to rework how we serialize the message since you're adding your own headers that are not specified in the generated web service code (so we end up not serializing your custom headers at all, they're completely ignored).

If you're interested in a quick fix/workaround I can implement GetWriterForMessage, then you can massage the xml yourself, injecting your header there, instead of adding it to the message. A complete fix will take a bit longer to implement though.
Comment 5 PJ 2013-11-19 16:44:59 UTC
This bug was targeted for a past milestone, moving to the next non-hotfix active milestone.
Comment 6 Rolf Bjarne Kvinge [MSFT] 2015-04-16 10:39:16 UTC
This will probably be fixed once we complete importing the reference code from Microsoft.