[Mono-bugs] [Bug 78953][Wis] New - WebServiceBinding - Namespace fails with xsp2

[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 ccirstea at saguaronet.ro.

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

--- shadow/78953	2006-07-26 05:31:57.000000000 -0400
+++ shadow/78953.tmp.25490	2006-07-26 05:31:57.000000000 -0400
@@ -0,0 +1,92 @@
+Bug#: 78953
+Product: Mono: Tools
+Version: unspecified
+OS: Solaris 8
+OS Details: SunOS 5.8
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: XSP
+AssignedTo: gonzalo at ximian.com                            
+ReportedBy: ccirstea at saguaronet.ro               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Summary: WebServiceBinding - Namespace fails with xsp2
+
+Please fill in this template when reporting a bug, unless you know what you 
+are doing.
+Description of Problem:
+
+The WebServiceBinding seems to fail when we specify a local binding and a 
+Namespace.
+
+If the Namespace is not specified the SoapDocumentMethod seems to work with 
+the local binding (also on xsp2).
+
+This issue arises only when running with xsp2. On xsp1 it is working OK.
+
+Attached I'm sending you a simple webservice that simulate the error. 
+
+
+Steps to reproduce the problem:
+1. Deploy the test.asmx on xsp2
+2. run it with any web browser
+3. 
+
+Actual Results:
+ON xsp2:
+
+Description: Error processing request. 
+
+Error Message: HTTP 500. 
+
+Stack Trace: 
+
+System.InvalidOperationException: Document 'http://192.168.101.220/Calin/
+test.asmx?wsdl=1' not found (Import 'http://192.168.101.220/Calin/test.
+asmx?wsdl=1' in Service Description 'www.DefaultNamespace.org')
+in <0x00068> System.Web.Services.Description.ConformanceCheckContext:
+ReportError (System.Object currentObject, System.String msg)
+in <0x00114> System.Web.Services.Description.BasicProfileChecker:Check 
+(System.Web.Services.Description.ConformanceCheckContext ctx, System.Web.
+Services.Description.Import value)
+in <0x00164> System.Web.Services.Description.WebServicesInteroperability:
+Check (System.Web.Services.Description.ConformanceCheckContext ctx, System.
+Web.Services.Description.ConformanceChecker checker, System.Web.Services.
+Description.ServiceDescription sd)
+in <0x00158> System.Web.Services.Description.WebServicesInteroperability:
+Check (WsiClaims claims, System.Web.Services.Description.
+ConformanceCheckContext ctx, IEnumerable documents)
+in <0x00040> System.Web.Services.Description.WebServicesInteroperability:
+CheckConformance (WsiClaims claims, System.Web.Services.Description.
+ServiceDescriptionCollection services, System.Web.Services.Description.
+BasicProfileViolationCollection violations)
+in <0x008ac> ASP.DefaultWsdlHelpGenerator_aspx:Page_Load (System.Object 
+sender, System.EventArgs e)
+in (wrapper delegate-invoke) System.MulticastDelegate:
+invoke_void_object_EventArgs (object,System.EventArgs)
+in <0x001b0> System.Web.UI.Control:OnLoad (System.EventArgs e)
+in <0x0019c> System.Web.UI.Control:LoadRecursive ()
+in <0x00298> System.Web.UI.Page:InternalProcessRequest ()
+in <0x000e4> System.Web.UI.Page:ProcessRequest (System.Web.HttpContext 
+context)
+
+
+ON XSP1
+
+Works OK
+
+
+Expected Results:
+
+No errors
+
+How often does this happen? 
+Always
+
+Additional Information:
+
+The tests has been originally run with Apache and mod_mono.
+But the same result arises when running directly with xsp and xsp2