[Mono-bugs] [Bug 60379][Wis] New - WSDL disparity between services on XSP and IIS

[bugzilla-daemon@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 rlyon@novell.com.

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

--- shadow/60379	2004-06-17 18:21:39.000000000 -0400
+++ shadow/60379.tmp.19614	2004-06-17 18:21:39.000000000 -0400
@@ -0,0 +1,53 @@
+Bug#: 60379
+Product: Mono: Class Libraries
+Version: unspecified
+OS: All
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: Sys.Web.Services
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: rlyon@novell.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: WSDL disparity between services on XSP and IIS
+
+Please fill in this template when reporting a bug, unless you know what 
+you are doing.
+Description of Problem:
+
+While the WSDLs between IIS and XSP are formatted differently, the only 
+difference that concerns me is in the SOAPActionURI.  XSP WSDL generates 
+the SOAPActionURIs with an addtional "/encodedTypes" path in the URI of 
+the action.  IIS WSDL generates a "/encodedTypes" path with encoded types 
+like XSP, but not in the SOAP actions.  The end result is that Apache 
+AXIS creates proxies where everything lines up except the SOAP actions.
+
+
+Steps to reproduce the problem:
+1. Create a web service and host it on IIS and XSP. 
+2. Use apache AXIS to create proxies.
+3. Compare the proxy code or try to use a one of the proxies against both 
+servers.
+
+Actual Results:
+
+A single proxy can not be used to access the same web service on XSP and 
+IIS.
+
+Expected Results:
+
+A single proxy should be able to access the same web service on XSP and 
+IIS.
+
+How often does this happen? 
+
+Always.
+
+Additional Information:
+
+None.