DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=36675>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36675

           Summary: Difficult to identify problems in JoranConfigurator
           Product: Log4j
           Version: 1.3alpha
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Configurator
        AssignedTo: log4j-dev@logging.apache.org
        ReportedBy: carnold@apache.org


The existing configurators swallow exceptions that occur in processing the XML or properties file.  While 
the silent approach is appropriate for default configuration.  If an application is making explicit calls to the 
configurator, there should be some manner for it to make a call where exceptions will be propagated to 
the caller.

See http://marc.theaimsgroup.com/?l=log4j-dev&m=110202005517575&w=2 ("Joran not reporting 
config errors", 12/04 on log4j-dev) and
http://marc.theaimsgroup.com/?l=log4j-user&m=112674335019978&w=2 ("DOMConfigurator configure 
methods do not report failure", 9/05 on log4j-user).

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org