Bug 6339 - Headers not being populated in SoapExtension
Summary: Headers not being populated in SoapExtension
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.Web.Services (show other bugs)
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-07-31 11:41 UTC by Bryan Moulton
Modified: 2016-11-11 09:41 UTC (History)
4 users (show)

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


Attachments
Test Project and WSDL (17.35 KB, application/zip)
2012-07-31 11:41 UTC, Bryan Moulton
Details

Description Bryan Moulton 2012-07-31 11:41:00 UTC
Created attachment 2282 [details]
Test Project and WSDL

When a web service uses custom Soap headers, the Microsoft .NET implementation of SoapExtension.ProcessMessage populates the message.Headers list during the AfterDeserialize stage. In the Mono implementation, no headers are listed.

Attached is a test project with WSDL. Running this project in Visual Studio and MonoDevelop reflects this difference in behavior.
Comment 1 Zoltan Varga 2012-08-09 00:02:19 UTC
-> class libs.

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.


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

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • 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


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.

Related Links: