log4cpp::PropertyConfiguratorImpl - Man Page

typedef std::map< std::string, Appender * > AppenderMap

PropertyConfiguratorImpl ()
virtual ~PropertyConfiguratorImpl ()
virtual void doConfigure (const std::string &initFileName)
virtual void doConfigure (std::istream &in)

void configureCategory (const std::string &categoryname)
configure the given category.
void getCategories (std::vector< std::string > &categories) const
Get a list of categories for which we should do the configuration.
void instantiateAllAppenders ()
Appender * instantiateAppender (const std::string &name)
Intantiate and configure the appender referred to by the given name.
void setLayout (Appender *appender, const std::string &name)
Method for instantiating and configuring the layouts associated with each appender.

Properties _properties
AppenderMap _allAppenders

configure the given category. This includes setting its Priority and adding any Appenders.

Todo

setting other properties like 'additivity'.

Parameters

categoryname Name of the category to configure. The name 'rootCategory' refers to the root Category.

Exceptions

ConfigureFailure if the method encountered a read or syntax error.

Parameters

initFileName

Exceptions

ConfigureFailure if the method encountered a read or syntax error.

Parameters

in

Exceptions

ConfigureFailure if the method encountered a read or syntax error.

Get a list of categories for which we should do the configuration. Get the categories contained within the map of properties.

This simply extracts the categories from the map.

Parameters

categories Reference to a list which is to receive the list of categories.

Since the category looks something like 'category.xxxxx.yyy.zzz', we need to search the entire map to figure out which properties are category listings. Seems like there might be a more elegant solution.

Intantiate and configure the appender referred to by the given name. This method searches the map to find all configuration parameters for the appender, and adds the appender to the given category. This isn't very general in the sense that it will need to be modified for each type of appender and layout. A more general solution would be to define an 'options' interface for each appender and layout, so that we can simply call this method with a list of options instead of needing to know what is or is not available. This would also require some generic way of instantiating an object for which we have no knowledge. An 'AppenderFactory' could be used which maps the given type to an actual object class registered with the factory (?? is this possible?).

Parameters

name String containing the name of the type of appender to be instantiated.

Method for instantiating and configuring the layouts associated with each appender.

Parameters

appender Appender to which we are setting this layout.
name Name in the properties of this appender.