Order in the file doesn't really matter in either case it seems. For a properties file, PropertyConfigurator does process entries in a specific order, but it just finds them in the properties file and builds the entries - here is the code from PropertyConfigurator:
configureRootCategory(properties, hierarchy); configureLoggerFactory(properties); parseCatsAndRenderers(properties, hierarchy); For an xml file, the elements will be processed as they are defined in the xml file - the DOMConfigurator code parses whatever is found in that order. Scott On Thu, Feb 2, 2012 at 5:19 AM, Stadelmann Josef < [email protected]> wrote: > Looks as if nobody knows it ... > > well, I have the sources and can look myself, > but I was so confident that a developer would know it :-( > > Josef > > -----Ursprüngliche Nachricht----- > Von: Stadelmann Josef [mailto:[email protected]] > Gesendet: Donnerstag, 26. Januar 2012 13:37 > An: [email protected] > Betreff: Configuration Sequence > > I have a simpel question : > > what is the prioper sequence in configuring log4j.properties > > 1. logger > 2. additivity > 3. appenders > 4. filters > > to reach that all gets parsed but not twice, > > if sequences are not correct, I see errors such as, in case of a rolling > file appender > file locked by another user, or in case of a Chainsaw sockethuappender, > socket > address already in use. > > What is the rule of dumb in configuration when tomcat startsup and has > to deploy / lauch axis2.war > > Josef > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
