Log4php can not only log string messages but also objects which will be converted to strings using either the default renderer or a customized render class.
Example:
require_once dirname(__FILE__).'/../../main/php/Logger.php';
Logger::configure(dirname(__FILE__).'/../resources/renderer_map.properties');
class Person {
public $firstName = 'John';
public $lastName = 'Doe';
}
class PersonRenderer implements LoggerRendererObject {
public function render($o) {
return $o->lastName.', '.$o->firstName;
}
}
$person = new Person();
$logger = Logger::getRootLogger();
$logger->debug("Now comes the current Person object:");
$logger->debug($person);
log4php.renderer.Person = PersonRenderer log4php.appender.default = LoggerAppenderEcho log4php.appender.default.layout = LoggerLayoutSimple log4php.rootLogger = DEBUG, default
Will output the following (notice how $person shows up in the output):
DEBUG - Now comes the current MyClass object: DEBUG - Doe, John
or the following if the default renderer were used:
DEBUG - Now comes the current MyClass object:
DEBUG - Person::__set_state(array(
'firstName' => 'John',
'lastName' => 'Doe',
))
Object rendering follows the class hierarchy. For example, assuming oranges are fruits, if you register an FruitRenderer, all fruits including oranges will be rendered by the FruitRenderer, unless of course you registered an orange specific OrangeRenderer.
Object renderers have to implement the LoggerRendererObject interface.
The XML configuration would look like this:
<log4php:configuration xmlns:log4php="http://logging.apache.org/log4php/">
<renderer renderedClass="Person" renderingClass="PersonRenderer" />
<appender threshold="WARN" name="default" class="LoggerAppenderEcho">
...