I don't think this is a good idea. The primary way to communicate with an application using SoapServer is via a soap client, and that client expects XML output for the error, it won't be able to parse a normal PHP exception output.

I don't think this is a good idea. The primary way to communicate with an application using SoapServer is via a soap client, and that client expects XML output for the error, it won't be able to parse a normal PHP exception output.

I don't see how these are any different from the TypeErrors thrown by ZPP? And we already throw ValueErrors in other SoapServer methods.

If those were commands sent by a client then I would agree, but this is configuring the SOAP server by someone, and those errors should never even be seen by a client.