[Mono-bugs] [Bug 51087][Wis] New - can't create xml-rpc.net web service

[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 james@ximian.com.

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

--- shadow/51087	2003-11-17 17:07:07.000000000 -0500
+++ shadow/51087.tmp.12946	2003-11-17 17:07:07.000000000 -0500
@@ -0,0 +1,75 @@
+Bug#: 51087
+Product: Mono/Runtime
+Version: unspecified
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Wishlist
+Component: misc
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: james@ximian.com               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: can't create xml-rpc.net web service
+
+So, we need to use Cook Computing's xml-rpc.net library with mono to create
+xmlrpc-based web services.  I followed the directions at
+http://www.xml-rpc.net/faq/xmlrpcnetfaq.html#How_do_I_implement_an_XML-RPC_server_in_IIS
+to setup a web.config and a sample service.  I created a directory 'bin'
+and put the service dll (snorpservice.dll) there.  I put the web.config in
+the server root directory, which reads as follows:
+
+<configuration>
+  <system.web>
+    <httpHandlers>
+      <add verb="*" path="SnorpService.rem"
+         type="SnorpService, snorpservice" />
+    </httpHandlers>
+  </system.web>
+<configuration>
+
+Then I ran 'mono xsp.exe --applications /xmlrpc:.' and attempted to access
+http://localhost:8080/xmlrpc/bin/SnorpService.rem with a browser (it is
+supposed to show a help page).  The browser shows a 500 error, and the
+server spews the following backtrace:
+
+System.NullReferenceException: A null value was found where an object
+instance was required
+ 
+Server stack trace:
+in <0x0001b>
+System.Runtime.Remoting.Messaging.CADMessageBase:SaveLogicalCallContext
+(System.Runtime.Remoting.Messaging.IMethodMessage,System.Collections.ArrayList&)
+in <0x0018a> System.Runtime.Remoting.Messaging.CADMethodReturnMessage:.ctor
+(System.Runtime.Remoting.Messaging.IMethodReturnMessage)
+in <0x00060>
+System.Runtime.Remoting.Messaging.CADMethodReturnMessage:Create
+(System.Runtime.Remoting.Messaging.IMessage)
+in <0x0008e> System.AppDomain:ProcessMessageInDomain
+(byte[],System.Runtime.Remoting.Messaging.CADMethodCallMessage,byte[]&,System.Runtime.Remoting.Messaging.CADMethodReturnMessage&)
+in <0x0008d> (wrapper remoting-invoke-with-check)
+System.AppDomain:ProcessMessageInDomain
+(byte[],System.Runtime.Remoting.Messaging.CADMethodCallMessage,byte[]&,System.Runtime.Remoting.Messaging.CADMethodReturnMessage&)
+in <0x0004b>
+System.Runtime.Remoting.Channels.CrossAppDomainSink:ProcessMessageInDomain
+(byte[],System.Runtime.Remoting.Messaging.CADMethodCallMessage)
+ 
+ 
+Exception rethrown at [0]:
+ 
+in <0x00172> System.Runtime.Remoting.Proxies.RealProxy:PrivateInvoke
+(System.Runtime.Remoting.Proxies.RealProxy,System.Runtime.Remoting.Messaging.IMessage,System.Exception&,object[]&)
+in (unmanaged) /opt/gnome/lib/libmono.so.0(mono_raise_exception+0x1b)
+[0x4007b907]
+in (unmanaged) /opt/gnome/lib/libmono.so.0 [0x4008c005]
+in <0x00044> (wrapper remoting-invoke) System.AppDomain:DoCallBack
+(System.CrossAppDomainDelegate)
+in <0x00032> (wrapper remoting-invoke-with-check)
+System.AppDomain:DoCallBack (System.CrossAppDomainDelegate)
+in <0x00129> Mono.ASPNET.Worker:Run (object)
+
+Am I doing something wrong here, or is this a mono bug?