for testing and deploying your application
for finding and fixing issues
for empowering human code reviews
<?php
namespace WebStream\Exception;
/**
* ApplicationException
* @author Ryuichi TANAKA.
* @since 2014/05/05
* @version 0.4
*/
class DelegateException extends ApplicationException
{
* @var bool ハンドリング可否
private $isHandled;
* @var \Exception 例外オブジェクト
private $originException;
* constructor
* @param \Exception 例外オブジェクト
public function __construct(\Exception $originException)
parent::__construct($originException->getMessage(), 500, $originException);
$originException
object<Exception>
object<WebStream\Exception\Exception>|null
It seems like the type of the argument is not accepted by the function/method which you are calling.
In some cases, in particular if PHP’s automatic type-juggling kicks in this might be fine. In other cases, however this might be a bug.
We suggest to add an explicit type cast like in the following example:
function acceptsInteger($int) { } $x = '123'; // string "123" // Instead of acceptsInteger($x); // we recommend to use acceptsInteger((integer) $x);
$this->originException = $originException;
$this->isHandled = false;
}
* オリジナルの例外を返却する
* @return \Exception 例外オブジェクト
public function getOriginException()
return $this->originException;
* ハンドリング可否を返却する
* @return bool ハンドリング可否
public function isHandled()
return $this->isHandled;
* ハンドリングを許可する
public function enableHandled()
$this->isHandled = true;
webstream-framework /
Exception
It seems like the type of the argument is not accepted by the function/method which you are calling.
In some cases, in particular if PHP’s automatic type-juggling kicks in this might be fine. In other cases, however this might be a bug.
We suggest to add an explicit type cast like in the following example: