-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exception wrapping #16
Comments
Happy to accept a pull request to support this -- I personally do not have time to implement this at time of writing. |
Great, will see if I do 👍 |
@SamMousa can you describe a bit more what you need or willing to achieve? Maybe I can help also.. |
The goal is to be able to identify errors based on the exception class only. try {
$client->doSomething();
} catch(TransIp\NotAllowedException $e) {
} catch(SomeOtherException $e) {
} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be great if this library mapped error responses to exception classes.
Currently when using this we are forced to check the
faultstring
andfaultcode
properties ofSoapFaults
, this breaks the API abstraction.The text was updated successfully, but these errors were encountered: