【发布时间】：2015-06-08 22:25:19
【问题描述】：
我想在 Apigility Zend Framework 2 应用程序中构建错误处理和日志记录机制，并捕获和记录所有异常。
经过一番研究，我发现了一个 Stack Overflow answer 的解决方案，它似乎完全符合这个要求。这是答案中的代码（有一些小的命名和格式修改）：
Module.php
...
use Zend\Mvc\ModuleRouteListener;
use Zend\Log\Logger;
use Zend\Log\Writer\Stream;
...
class Module implements ApigilityProviderInterface
{
public function onBootstrap(MvcEvent $mvcEvent)
{
$eventManager = $mvcEvent->getApplication()->getEventManager();
$moduleRouteListener = new ModuleRouteListener();
$moduleRouteListener->attach($eventManager);
/**
* Log any Uncaught Exceptions, including all Exceptions in the stack
*/
$sharedEventManager = $mvcEvent->getApplication()->getEventManager()->getSharedManager();
$serviceManager = $mvcEvent->getApplication()->getServiceManager();
$sharedEventManager->attach('Zend\Mvc\Application', MvcEvent::EVENT_DISPATCH_ERROR,
function($mvcEvent) use ($serviceManager) {
if ($mvcEvent->getParam('exception')){
$exception = $mvcEvent->getParam('exception');
do {
$serviceManager->get('Logger')->crit(
sprintf(
"%s:%d %s (%d) [%s]\n",
$exception->getFile(),
$exception->getLine(),
$exception->getMessage(),
$exception->getCode(),
get_class($exception)
)
);
}
while($exception = $exception->getPrevious());
}
}
);
}
...
public function getServiceConfig() {
return array(
'factories' => array(
// V1
...
'Logger' => function($sm){
$logger = new Logger;
$writer = new Stream('/var/log/httpd/sandbox-log');
$logger->addWriter($writer);
return $logger;
},
),
...
);
}
}
所以现在我已经在代码中的几个地方（Resource、Service 和 Mapper 类）尝试了这个（用一个简单的throw new \Exception('foo')）并期望得到缓存的异常并登录到我定义的文件中。但它不起作用。
我做错了吗？什么？如何让它工作？ 如何在 Apigility 驱动的 Zend Framework 2 应用程序中捕获和记录所有异常？
附加信息：代码中引发异常的位置示例：
class AddressResource extends AbstractResourceListener ...
{
public function fetch($id) {
throw new \Exception('fetch_EXCEPTION');
$service = $this->getAddressService();
$entity = $service->getAddress($id);
return $entity;
}
}
附加信息：响应中的跟踪（如果在BarResource#fetch(...) 中设置throw new \Exception('fetch_EXCEPTION');）：
{
"trace": [
{
"file": "/var/www/my-project/vendor/zfcampus/zf-rest/src/AbstractResourceListener.php",
"line": 166,
"function": "fetch",
"class": "FooAPI\\V1\\Rest\\Bar\\BarResource",
"type": "->",
"args": [
"1"
]
},
{
"function": "dispatch",
"class": "ZF\\Rest\\AbstractResourceListener",
"type": "->",
"args": [
{}
]
},
{
"file": "/var/www/my-project/vendor/zendframework/zendframework/library/Zend/EventManager/EventManager.php",
"line": 444,
"function": "call_user_func",
"args": [
[
{},
"dispatch"
],
{}
]
},
{
"file": "/var/www/my-project/vendor/zendframework/zendframework/library/Zend/EventManager/EventManager.php",
"line": 205,
"function": "triggerListeners",
"class": "Zend\\EventManager\\EventManager",
"type": "->",
"args": [
"fetch",
{},
{}
]
},
{
"file": "/var/www/my-project/vendor/zfcampus/zf-rest/src/Resource.php",
"line": 541,
"function": "trigger",
"class": "Zend\\EventManager\\EventManager",
"type": "->",
"args": [
{},
{}
]
},
{
"file": "/var/www/my-project/vendor/zfcampus/zf-rest/src/RestController.php",
"line": 483,
"function": "fetch",
"class": "ZF\\Rest\\Resource",
"type": "->",
"args": [
"1"
]
},
{
"file": "/var/www/my-project/vendor/zendframework/zendframework/library/Zend/Mvc/Controller/AbstractRestfulController.php",
"line": 366,
"function": "get",
"class": "ZF\\Rest\\RestController",
"type": "->",
"args": [
"1"
]
},
{
"file": "/var/www/my-project/vendor/zfcampus/zf-rest/src/RestController.php",
"line": 332,
"function": "onDispatch",
"class": "Zend\\Mvc\\Controller\\AbstractRestfulController",
"type": "->",
"args": [
{}
]
},
{
"function": "onDispatch",
"class": "ZF\\Rest\\RestController",
"type": "->",
"args": [
{}
]
},
{
"file": "/var/www/my-project/vendor/zendframework/zendframework/library/Zend/EventManager/EventManager.php",
"line": 444,
"function": "call_user_func",
"args": [
[
{},
"onDispatch"
],
{}
]
},
{
"file": "/var/www/my-project/vendor/zendframework/zendframework/library/Zend/EventManager/EventManager.php",
"line": 205,
"function": "triggerListeners",
"class": "Zend\\EventManager\\EventManager",
"type": "->",
"args": [
"dispatch",
{},
{}
]
},
{
"file": "/var/www/my-project/vendor/zendframework/zendframework/library/Zend/Mvc/Controller/AbstractController.php",
"line": 118,
"function": "trigger",
"class": "Zend\\EventManager\\EventManager",
"type": "->",
"args": [
"dispatch",
{},
{}
]
},
{
"file": "/var/www/my-project/vendor/zendframework/zendframework/library/Zend/Mvc/Controller/AbstractRestfulController.php",
"line": 300,
"function": "dispatch",
"class": "Zend\\Mvc\\Controller\\AbstractController",
"type": "->",
"args": [
{},
{}
]
},
{
"file": "/var/www/my-project/vendor/zendframework/zendframework/library/Zend/Mvc/DispatchListener.php",
"line": 93,
"function": "dispatch",
"class": "Zend\\Mvc\\Controller\\AbstractRestfulController",
"type": "->",
"args": [
{},
{}
]
},
{
"function": "onDispatch",
"class": "Zend\\Mvc\\DispatchListener",
"type": "->",
"args": [
{}
]
},
{
"file": "/var/www/my-project/vendor/zendframework/zendframework/library/Zend/EventManager/EventManager.php",
"line": 444,
"function": "call_user_func",
"args": [
[
{},
"onDispatch"
],
{}
]
},
{
"file": "/var/www/my-project/vendor/zendframework/zendframework/library/Zend/EventManager/EventManager.php",
"line": 205,
"function": "triggerListeners",
"class": "Zend\\EventManager\\EventManager",
"type": "->",
"args": [
"dispatch",
{},
{}
]
},
{
"file": "/var/www/my-project/vendor/zendframework/zendframework/library/Zend/Mvc/Application.php",
"line": 314,
"function": "trigger",
"class": "Zend\\EventManager\\EventManager",
"type": "->",
"args": [
"dispatch",
{},
{}
]
},
{
"file": "/var/www/my-project/public/index.php",
"line": 56,
"function": "run",
"class": "Zend\\Mvc\\Application",
"type": "->",
"args": []
}
],
"type": "http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html",
"title": "Internal Server Error",
"status": 500,
"detail": "fetch_EXCEPTION"
}
【问题讨论】：
-
问题是没有到达回调函数还是日志没有工作？您是否尝试过以更高的优先级附加您的听众，即
> 1？ -
没错，回调根本没有到达。它适用于另一个 ZF2 应用程序，但在这里，在“Apigility 应用程序”中，它似乎被忽略了。我刚刚尝试更改优先级（
1000和-1000），但没有帮助。
标签： logging exception-handling zend-framework2 laminas-api-tools exception-logging