Bug 39024 - DOMConfigurator not compatible for extension and missing public methods
Summary: DOMConfigurator not compatible for extension and missing public methods
Status: RESOLVED WONTFIX
Alias: None
Product: Log4j - Now in Jira
Classification: Unclassified
Component: Configurator (show other bugs)
Version: 1.3alpha
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: log4j-dev
URL:
Keywords:
Depends on:
Blocks: 35452
  Show dependency tree
 
Reported: 2006-03-18 04:16 UTC by Curt Arnold
Modified: 2007-08-09 14:53 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Curt Arnold 2006-03-18 04:16:33 UTC 
The SVN HEAD contains a DOMConfigurator that delegates to JoranConfigurator for
implementation.  The current implementation is missing three public methods
exposed by log4j 1.2's DOMConfigurator: 

void configurationAndWatch(String);
void configurationAndWatch(String, long);
void doConfigure(Reader, LoggerRepository);

In addition, any DOMConfiguration extensions are highly likely to be broken due
to the change of the internal structure.  While less common than extended RFA's,
extensions of DOMConfigurator are likely to exist and should be supported. 
Given the radical difference in the DOMConfigurator and JoranConfigurator
implementation, porting the log4j 1.2 DOMConfigurator forward would seem the
reasonable approach.  Though like the o.a.l.RFA's, DOMConfigurator would be
marked as deprecated and could be placed in a log4j-obsolete.jar.
Comment 1 Curt Arnold 2007-08-09 14:53:38 UTC 
log4j 1.3 development has been suspended and further work on compatibility is not expected.