[jsword-devel] [JIRA] Updated: (JS-107) JSword Common Logger readConfiguration problem

[DM Smith (JIRA)]

     [ http://www.crosswire.org/bugs/browse/JS-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

DM Smith updated JS-107:
------------------------

    Fix Version/s: 1.6.1

> JSword Common Logger readConfiguration problem
> ----------------------------------------------
>
>                 Key: JS-107
>                 URL: http://www.crosswire.org/bugs/browse/JS-107
>             Project: JSword
>          Issue Type: Bug
>            Reporter: Tonny Kohar
>            Assignee: DM Smith
>            Priority: Minor
>             Fix For: 1.6.1
>
>
> Hi, 
> I would like to propose a change to JSword Common Logger (org.crosswire.common.util.Logger) readConfiguration, because currently it is setting/re-applying its configuration to the global setting of java.logging. This can cause problem because many third party library which also use java.logging will get its configuration changed (reseted) as well.
> IMHO, this kind of configuration setting should be in application specific (eg: BibleDesktop, Alkitab, etc) rather than in common library.
> So I propose to
> - move the readConfiguration from org.crosswire.common.util.Logger (establishLogging -> readConfiguration) from common to application specific eg: BibleDesktop
> - or add the following public static method to org.crosswire.common.util.Logger which allow the user of the API to disable the readConfiguration
> public static void setEnableReadConfiguration(boolean b) {
>    established = b;
> }
> note: I found out this issue because the above readConfiguration re-applying/re-reading logger configuration
> will mess up Netbeans Platform (our platform framework which is used in Alkitab) logging.
> Cheers
> Tonny Kohar

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira