This is not acceptable server behavior -- server should not crash because of malformed XML message. I hope a bug has been filed.
Soumen Sarkar. -----Original Message----- From: Gopinadh Bandaru [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 13, 2001 5:04 AM To: '[EMAIL PROTECTED]' Subject: RE: problem with method name empty i too got the same problem previously I think if u call with wrong name or with wrong arguments the soap server is completely crashed and we have to start the server again... cheers gopi -----Original Message----- From: Davide Frigerio [mailto:[EMAIL PROTECTED]] Sent: 13 December 2001 12:57 To: [EMAIL PROTECTED] Subject: problem with method name empty Hi, I'was using SOAP since dicember 2000 but I'am just subscribe me to this mailing list. At the moment I'am working in a project about EAI problem's (www.wisemodel.com) and I integrted the SOAP services inside this architecture adopting the SOAP library by Apache. During the test-phase I notice a bug very interested; for error I sended a SOAP request using org.apache.soap.rpc.Call class with a null string by MethodName. The surprice was not that the service didn't work, I noticed that the SOAP server stop to work after recieveing this wrong SOAP request. Davide Frigerio www.wise-lab.it
