Issues

ZF-7751: Add support for extended fault codes

Issue Type: Improvement Created: 2009-09-02T03:31:06.000+0000 Last Updated: 2012-11-20T20:53:06.000+0000 Status: Closed Fix version(s): Reporter: Amr Mostafa (alienbrain) Assignee: None Tags: - Zend_Soap_Server

Related issues: Attachments:

Description

Currently when an exception with the code, e.g. 123 is thrown, it's converted to the Receiver fault code, since SOAP allows only a set of base faults: (Receiver, Sender, Server, MustUnderstand, VersionMismatch, DataEncodingUnknown).

However, SOAP also supports extending those base faults with your own codes. By using the . (dot) as a separator.

It would be nice if the server can support this standard notation.

Note: The challenge, which I think should be tackled in a separate issue once this is done, is to how to convert exception codes (Integers) to an extended fault. One way which we currently use is to throw My_Soap_Fault instead of SoapFault, and My_Soap_Fault is has a set of rules which it uses to convert an exception code, e.g. 123 to Sender.123, but 789 to Receiver.789.

Comments

Posted by Benjamin Eberlei (beberlei) on 2009-09-04T13:23:53.000+0000

This sounds good, however i have to think about the API

Posted by Rob Allen (rob) on 2012-11-20T20:53:06.000+0000

Bulk change of all issues last updated before 1st January 2010 as "Won't Fix".

Feel free to re-open and provide a patch if you want to fix this issue.

Have you found an issue?

See the Overview section for more details.

Copyright

© 2006-2016 by Zend, a Rogue Wave Company. Made with by awesome contributors.

This website is built using zend-expressive and it runs on PHP 7.

Contacts