Hi all, the Spring framework offers inheritance for their xml configuration. http://static.springsource.org/spring/docs/3.2.2.RELEASE/spring-framework-re... Maybe you can get some inspiration from it. For instance, you have to identify the elements you want to override. Spring uses the bean name for it and a parent-attribute. Logback may use the type (appender, logger, etc.) and the name. Spring offers an import mechanism: you can define a path and/or name templates to scan for additional files ("Composing XML-based configuration metadata"). This would also reduce classloading issues, because you always look for the defined (or default) logback configuration (f.i. logback.xml) and then import additional files (f.i. logback\logback-extended.xml) Regards, Johannes -----Ursprüngliche Nachricht----- Von: Logback-user [mailto:logback-user-bounces@qos.ch] Im Auftrag von David Roussel Gesendet: Sonntag, 5. Mai 2013 19:29 An: logback users list Betreff: Re: [logback-user] Multiple logback.xml, configuration merging/inheritance Can you implement what you want with file inclusion? David On 5 May 2013, at 17:16, cowwoc <cowwoc@bbs.darktech.org> wrote:
Hi,
Is it possible to discuss http://jira.qos.ch/browse/LOGBACK-857 on this list? I'd like to get your feedback.
I would send you a patch if I could, but I'm not sure how to implement the actual configuration merging process.
Gili _______________________________________________ Logback-user mailing list Logback-user@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user
Logback-user mailing list Logback-user@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user ________________________________ Firma: Capgemini Deutschland GmbH Geschäftsführer: Dr. Michael Schulte (Sprecher) • Dr. Uwe Dumslaff • Josef Ranner Aufsichtsratsvorsitzender: Antonio Schnieder Amtsgericht Berlin-Charlottenburg, HRB 98814 This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.