I solved this by modifying the call_user_func*() calls in SOAP_Server::callMethod() which all used the @ operator to suppress errors, which seems to suppress this particular error. I for one can't see the use of the '@' in this instance, but does anyone know if removing it will have any repercussions? Tristan. > -----Original Message----- > From: Javier Muniz [mailto:jmuniz@granicus.com] > Sent: Wednesday, 10 September 2003 12:25 PM > To: 'LIMBOURG Arnaud'; soap@lists.php.net > Subject: RE: [SOAP] soap problems revisited > > > I don't think display_errors is the culprit when a class is > not defined. On my server I have display_errors set to on > but I am still getting an empty soap_fault object when I try > to instatiate a class that has not been defined. This is a > pretty huge hassle when trying to debug a large application > implemented with PEAR::SOAP :) > > -Javier -- PHP Soap Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
