RealObjects Support

When integrating PDFreactor, especially during the trial and development phases, it might be useful to retrieve debugging information about the conversion. The most convenient way to do this is by enabling the various debugging tools of PDFreactor. This can be done in the configuration like this:

Java

config.setDebugSettings(new DebugSettings().setAll(true));
config.setContentObserver(new ContentObserver()
    .setMissingResources(true)
    .setConnections(true));

config.DebugSettings = new DebugSettings { All: true };
config.ContentObserver = new ContentObserver
{
    MissingResources = true,
    Connections = true
};

config.debugSettings = { all: true };
config.contentObserver {
    missingResources: true,
    connections: true
};

$config["debugSettings"] = array("all" => true);
$config["contentObserver"] = array(
    "missingResources" => true,
    "connections" => true
);

config['debugSettings'] = { "all": True }
config['contentObserver'] = {
    "missingResources": True,
    "connections": True
}

config['debugSettings'] = { "all": true }
config['contentObserver'] = {
    "missingResources": true,
    "connections": true
}

$config["debugSettings"] = { "all" => true };
$config["contentObserver"] = {
    "missingResources" => true,
    "connections" => true
};

{ "debugSettings": { "all": true },
  "contentObserver": {
    "missingResources": true,
    "connections": true
}}

--enableDebugMode -C config.json

With the following config.json:

{ "contentObserver": {
    "missingResources": true,
    "connections": true
}}

The debug mode will by default append a log to the generated PDF as well as attach certain files which relevant debugging information. More information about the exact behavior can be found in the PDFreactor manual.