[Mono-bugs] [Bug 79017][Wis] New - ConfigurationException: Duplicate element in collection ()

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by tonyxgu at yahoo.com.

http://bugzilla.ximian.com/show_bug.cgi?id=79017

--- shadow/79017	2006-08-04 20:17:48.000000000 -0400
+++ shadow/79017.tmp.19501	2006-08-04 20:17:48.000000000 -0400
@@ -0,0 +1,81 @@
+Bug#: 79017
+Product: Mono: Class Libraries
+Version: 1.1
+OS: 
+OS Details: RedHat 9.0
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: Sys.Web.Services
+AssignedTo: lluis at ximian.com                            
+ReportedBy: tonyxgu at yahoo.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: ConfigurationException: Duplicate element in collection ()
+
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+When web.config has the elements under <webServices><protocols> tag, the
+webService application throws ConfigurationException
+
+Steps to reproduce the problem:
+1. Add the following setction under <system.web> tag in web.config file:
+      <webServices>
+         <protocols>
+            <add name="HttpGet"/>
+            <add name="HttpPost"/>
+          </protocols>
+       </webServices>
+2. Run the webSvc application.
+3. 
+
+Actual Results:
+System.Configuration.ConfigurationException: Duplicate element in collection ()
+  at System.Configuration.ConfigurationElementCollection.BaseAdd
+(System.Configuration.ConfigurationElement element, Boolean throwIfExists)
+[0x00000] 
+  at System.Configuration.ConfigurationElementCollection.BaseAdd
+(System.Configuration.ConfigurationElement element) [0x00000] 
+  at
+System.Configuration.ConfigurationElementCollection.OnDeserializeUnrecognizedElement
+(System.String elementName, System.Xml.XmlReader reader) [0x00000] 
+  at System.Configuration.ConfigurationElement.DeserializeElement
+(System.Xml.XmlReader reader, Boolean serializeCollectionKey) [0x00000] 
+  at System.Configuration.ConfigurationElement.DeserializeElement
+(System.Xml.XmlReader reader, Boolean serializeCollectionKey) [0x00000] 
+  at System.Configuration.ConfigurationSection.DeserializeSection
+(System.Xml.XmlReader reader) [0x00000] 
+  at System.Configuration.Configuration.GetSectionInstance
+(System.Configuration.SectionInfo config, Boolean createDefaultInstance)
+[0x00000] 
+  at System.Configuration.ConfigurationSectionCollection.get_Item
+(System.String name) [0x00000] 
+  at System.Configuration.Configuration.GetSection (System.String path)
+[0x00000] 
+  at
+System.Web.Configuration.WebConfigurationManager.GetWebApplicationSection
+(System.String sectionName) [0x00000] 
+  at System.Web.Services.Configuration.WebServicesSection.get_Instance ()
+[0x00000] 
+  at System.Web.Services.Configuration.WebServicesSection.IsSupported
+(WebServiceProtocols proto) [0x00000] 
+  at System.Web.Services.Protocols.WebServiceHandlerFactory.GetHandler
+(System.Web.HttpContext context, System.String verb, System.String url,
+System.String filePath) [0x00000] 
+  at System.Web.HttpApplication.GetHandler (System.Web.HttpContext context)
+[0x00000] 
+  at System.Web.HttpApplication+<Pipeline>__2.MoveNext () [0x00000] 
+
+Expected Results:
+
+
+How often does this happen? 
+Always
+
+Additional Information:
+It is under Mono-1.1.16.1. The same web.config is OK under Mono-1.1.13.8
+(Well, the WebConfigurationManager is not implemented there)