[#ZF-3958] Wrong call for new SoapFault in Zend_Soap_Server::fault() breaks SOAP exception handling - Zend Framework Issue Tracker

Zend Framework

Wrong call for new SoapFault in Zend_Soap_Server::fault() breaks SOAP exception handling

Created: 15/Aug/08 06:22 AM Updated: 13/Nov/08 02:10 PM Resolved: 27/Oct/08 09:26 AM

Return to search "Fixed in 1.5.1"

Component/s:

Zend_Soap_Server

Affects Version/s:

1.5.0RC1, 1.5.0RC2, 1.5.0RC3, 1.5.0, 1.5.0PL1, 1.5.1, 1.5.2, 1.6.0RC1, 1.5.3, 1.6.0RC2, 1.6.0RC3, 1.6.0, 1.6.1, Next Major Release

Fix Version/s:

1.7.0

Time Tracking:

Not Specified

File Attachments:

Server.php.patch (0.4 kB)

Description

« Hide

SoapFault expects the code parameter being a string instead of an integer.
If code is an integer, the SoapException reports an internal server error instead of the correct one.

The correct call has to be:

return new SoapFault( (string) $code, message );

Sort Order:

[ Permalink | « Hide ]

T.Lechat added a comment - 29/Aug/08 05:30 AM

You're correct, line 799 of server.php needs to have (string) to works correctly. Now I can register Exception and use it in the handled class. Thanks.

[ Permalink | « Hide ]

Andy Thompson added a comment - 24/Sep/08 09:53 AM

Shouldn't this be considered high priority? It effectively breaks exception handling, as Exception->getCode() is always is an integer.

[ Permalink | « Hide ]

Patrick Schulz added a comment - 29/Sep/08 05:01 PM

This is the patch. I'm not sure if it is the correct format. Please give feedback.