Issue #840 has been reported by Harald Strack.

----------------------------------------
Feature #840: Make path to logging.xml configurable
http://tools.lsc-project.org/issues/840

Author: Harald Strack
Status: New
Priority: Normal
Assigned to: Clément OUDOT
Category: Core
Target version: 2.2


h2. Problem 

* When running LSC in embedded mode (e.g. as part of a Spring web application) 
the application usually has its own logging configuration. When we load LSC as 
part of the application, it initializes logback with the @logging.xml@ from the 
LSC configuration directory and overloads the application's configuration. 
* Since we use the same configuration directory (@/etc/lsc/@) for normal LSC 
cronjobs *and* for the embedded version, replacing the @logging.xml@ of LSC 
with the applications logging configuration is not an option

h2. Solution

* We allow LSC to override the logging path via a system property, patch 
proposal attached
* In our case that's fine, since the Spring application also uses logback but 
for other applications it may'd be better to be able to have an option to 
disable the logging configuration of LSC at all



-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://tools.lsc-project.org/my/account
_______________________________________________________________
Ldap Synchronization Connector (LSC) - http://lsc-project.org

lsc-dev mailing list
[email protected]
http://lists.lsc-project.org/listinfo/lsc-dev

Reply via email to