This would be nice for handling ZendFramework Exceptions to your own framwork or CMS Exceptions:
<?php
try
{
$oZFResponse = $oZFHttpClient->request();
}
catch(Zend_Http_Exception $exZFHttpEx)
{
throw new Runtime_{$oZFHttpEx->getCode()}_Exception('some ErrorMailing Message', 500, $oZFHttpEx);
}
?>
Regards,
Mario
Exception::__construct
(PHP 5 >= 5.1.0)
Exception::__construct — Constructor de la excepción
Descripción
public Exception::__construct()
([ string
$message = ""
[, int $code = 0
[, Exception $previous = NULL
]]] )Construye la Excepción.
Parámetros
-
message -
Mensaje de la Excepción a lanzar.
-
code -
El código de la Excepción.
-
previous -
La excepción previa usada por el encadenado de la excepción.
Historial de cambios
| Versión | Descripción |
|---|---|
| 5.3.0 |
Se añadió el parámetro previous.
|
Notas
Nota:
El
messageNO es seguro binariamente.
mario dot mueller at twt dot de ¶
4 years ago
mattsch at gmail dot com ¶
4 months ago
Be aware that while $previous is quite useful in providing exception chaining and better traceability, none of the internal php exceptions (e.g. PDOException, ReflectionException, etc) are called internally within php with $previous in mind.
So if your code throws an exception, recovers from it, then catches one of these internal php exceptions, recovers from it and throws another exception, you will not know the first exception that was thrown when calling getPrevious.
See: https://bugs.php.net/bug.php?id=63873
