Description

The DTD is specified in log4g.dtd. The Log4g DTD differs in some small ways from the official Log4j DTD.

Use "appender" everywhere instead of "appender-ref". Appenders may be declared inline to a logger. Appender references simply use a named "appender" tag and do not define a new appender.

Use "property" instead of "param". The keyword "property" was used instead of "param" to reflect the underlying GLib/GObject implementation.

The following configuration provides a cut-and-paste example:

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE log4g:configuration PUBLIC "-//GNOME//DTD LOG4G 1.0//EN"
    "http://www.gnome.org/log4g/1.0/log4g.dtd">
<log4g:configuration>
    <appender name="A1" type="Log4gConsoleAppender">
        <layout type="Log4gPatternLayout">
            <property name="conversion-pattern"
                      value="%-4r [%t] %-5p %c %x - %m%n" />
        </layout>
    </appender>
    <root>
        <level value="DEBUG" />
        <appender name="A1" />
    </root>
</log4g:configuration>

In this example all events will be logged to the console appender (stdout by default) using the specified pattern layout.

You may enable internal log messages by setting the LOG4G_FLAGS environment variable to "debug". For example (Bash):

$ export LOG4G_FLAGS=debug

Alternatively you may set the "debug" attribute in the log4g:configuration element:

<log4g:configuration debug="true">
</log4g:configuration>

Details

typedef struct {
} Log4gDOMConfigurator;

typedef struct {
} Log4gDOMConfiguratorClass;

Log4gConfigurator * log4g_dom_configurator_new          (void);

gboolean            log4g_dom_configurator_configure    (const gchar *uri,
                                                         GError **error);

See Also