Niclas Hedhman (JIRA)
Wed, 27 Jan 2010 18:50:16 -0800
[
http://issues.ops4j.org/browse/PAXLOGGING-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13299#action_13299
]
Niclas Hedhman commented on PAXLOGGING-71: ------------------------------------------ Feel free to put forward a proposal on how this is to be done. IMNSHO, Configuration Admin service is to be used. That pretty much limits the choice to "provide a URL to the XML file", which then leads to ambiguity issue of "what if there is both 'classic' configuration and 'dom' configuration" arriving at the ManagedService interface? Priority? Merging? > Add an additional PaxLoggingConfigurator based on DOMConfigurator > ----------------------------------------------------------------- > > Key: PAXLOGGING-71 > URL: http://issues.ops4j.org/browse/PAXLOGGING-71 > Project: Pax Logging > Issue Type: New Feature > Affects Versions: 1.4 > Environment: WinXp, Fuse 4.2 RC1 > Reporter: Mateusz Nowakowski > Assignee: Niclas Hedhman > > Current PaxLoggingConfigurator is based on log4j PropertyConfigurator what > has several limitations (support for filters, custom error handles, nested > appenders such as the log4j AsyncAppender) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.ops4j.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira _______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general