Somehow I totally missed this discussion. I was away at the time, and missed it when I got back...
First, Michael, there is a passage in the docs: http://logging.apache.org/log4php/docs/configuration.html which says: -- Hint: to translate a XML or properties configuration file to PHP, run the following code: $configurator = new LoggerConfiguratorDefault(); $config = $configurator->parse('/path/to/config.xml'); -- This will convert your .xml (or .properties) file to a config array. Second, I designed the array structure to be easy to parse and apply. Also, it made sense to me. It still lacks some docs, but there are a lot of examples floating around (at least one for each appender, layout and filter), and with the xml->php converter I thought we're more or less covered. There's always room for improvement, though. I plan to put some more effort into this for the next release. We're open for new ideas, but I really don't want to have 10 configuration formats if it's possible. :) Regards, Ivan On 17 May 2012 13:49, Florian Semm <florian.s...@gmx.de> wrote: > Am 16.05.2012 19:46, schrieb Michael Sole: > > Thanks!!!!! > > > > Not sure why this isn’t better documented. If multiple arrays didn’t make my > eyes bleed I would offer to doc this better. > > I think there is still an issue in JIRA "improve documentation", or > somethink like that. > > However it seems a more intuitive approach would make more sense. Something > like: > > > > Array(‘logger’ => array(‘param’=>’value’, ‘param2’=>’value’)); > > > Complex logger-structures cause complex config-structures. Some options of > log4php maybe not important than others, but you need a way to configure all > this options. > > Maybe it's possible to reduce the options of some components, which are not > needed. > > > > > Or something like that, we don’t need to completely mimic XML, I think > > > regards > > Florian
