|Is it possible to extend log configuration without touching serviceability.xml? [message #879187]
||Wed, 30 May 2012 13:42
| Rich Mayfield
Registered: August 2010
According to the documentation one updates serviceability.xml to change configuration of the logback back-end.|
What I'm wondering is if there is a way to extend this configuration on a per-application basis without touching that one file. I guess what I'm hoping to avoid are problems where multiple applications are reaching their grimy hands into that configuration file (and other configuration files) to do things like change "logger" settings or add "appender" implementations.
Right now, I'm touching these files to add my own appender:
configuration/org.eclipse.equinox.simpleconfigurator/bundles.info - to add my appender implementation fragment to logback.
configuration/org.ecilpse.virgo.kernel.userregion.properties - to allow my fragment to bleed through to the user region so that my application can change logging parameters at run time
configuration/serviceability.xml - to register my appenders/loggers
Is there any way to avoid this? Any way to package and deploy this with my application/plan?
Thanks much in advance.
Powered by FUDForum
. Page generated in 0.04183 seconds