Ugh. I never noticed that the admin GUI does not allow one to specify a fault listener.
To get to the bottom of this, I wrote my own sample client and service. I got the "no signature match" error when I passed a null DataHandler, because the Apache SOAP code serializes a DataHandler as xsd:anyType, which is always deserialized as an Object. I am not sure why you do not still see this message, too. Anyway, I made a small change to SOAPMappingRegistry so that a null DataHandler can be properly serialized and de-serialized. If you pick up the next nightly build, you will get that change. Both your client and server will need the new code. Scott Nichol ----- Original Message ----- From: "Praveen Peddi" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, January 08, 2003 11:44 AM Subject: Re: Urgent: Soap With attachments example > Even though I have a deployment descriptor and the line > <isd:faultListener>org.apache.soap.server.DOMFaultListener</isd:faultLis tene > r> is in a separate line, I deployed the services using the soap admin > client that apache provided. I got NoClassDefFound errors when I tried to > deploy using deployment descriptor. <<snip>> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
