Re: fault listener

I'll note two things:

1. If you can in your environment (e.g. it is not production), I suggest you use the nightly build of Apache SOAP (http://cvs.apache.org/dist/soap/nightly/2004-04-07/).  This fixes several bugs, adds a few features, and in particular will give you more using exception information in the area you are having problems.

2. One of the issues in 2.3.1 is that you will get the kind of generic error you see below if you include whitespace in the name of the fault listener class or misspell the class.  For example, having the following in the deployment descriptor will cause the exception you are seeing

  <isd:faultListener>org.apache.soap.server.DOMFaultListener
  </isd:faultListener>

because there is whitespace in the class name.  Check your deployment descriptor.

Scott Nichol

Do not send e-mail directly to this e-mail address,
because it is filtered to accept only mail from
specific mail lists.
----- Original Message ----- 
From: <[email protected]>
To: <[email protected]>
Sent: Monday, June 07, 2004 1:52 AM
Subject: fault listener


Hi there,

I have been testing some services with no faultListener at all, and everything
worked right. I have tryed DOMFaultListener, and it works ok too. But I
have a problem with ExceptionFaultListener. 

When there is no exception generated at the server side, it works fine.
But when there is an exception, I can't access to the Fault, because an
exception is generated on the client side, at the moment of invoking the
service (RPCCall.invoke(url.....). The exception message is the following:

[SOAPException: faultCode=SOAP-ENV:Protocol; msg=Unsupported response content
type &quot;text/html; charset=ISO-8859-1&quot;, must be: &quot;text/xml&quot;.
Response was:
&lt;html&gt;&lt;head&gt;&lt;title&gt;Apache Tomcat/5.0.18 - Informe de Error&lt;/title&gt;&lt;style&gt;&lt;!--H1
{font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;}
H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;}
H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;}
BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;}
B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;}
P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A
{color : black;}A.name {color : black;}HR {color : #525D76;}--&gt;&lt;/style&gt;
&lt;/head&gt;&lt;body&gt;&lt;h1&gt;Estado HTTP 500 - &lt;/h1&gt;&lt;HR size=&quot;1&quot;
noshade&gt;&lt;p&gt;&lt;b&gt;type&lt;/b&gt; Informe de Excepción&lt;/p&gt;&lt;p&gt;&lt;b&gt;mensaje&lt;/b&gt;
&lt;u&gt;&lt;/u&gt;&lt;/p&gt;&lt;p&gt;&lt;b&gt;descripción&lt;/b&gt; &lt;u&gt;El
servidor encontró un error interno () que hizo que no pudiera rellenar este
requerimiento.&lt;/u&gt;&lt;/p&gt;&lt;p&gt;&lt;b&gt;excepción&lt;/b&gt;
&lt;pre&gt;javax.servlet.ServletException: Error building response envelope:
java.lang.NullPointerException
        org.apache.soap.server.http.RPCRouterServlet.doPost(RPCRouterServlet.java:418)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:763)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
&lt;/pre&gt;&lt;/p&gt;&lt;p&gt;&lt;b&gt;nota&lt;/b&gt; &lt;u&gt;La traza
completa de la causa de este error se encuentra en los archivos de diario
de Tomcat.&lt;/u&gt;&lt;/p&gt;&lt;HR size=&quot;1&quot; noshade&gt;&lt;h3&gt;Apache
Tomcat/5.0.18&lt;/h3&gt;&lt;/body&gt;&lt;/html&gt;
]

Can anyone help me?, do yo need more information about this error?

Thanks very much,

tizo