https://issues.apache.org/bugzilla/show_bug.cgi?id=47960
--- Comment #4 from [email protected] 2009-10-08 15:54:02 PDT --- I have implemented a new CompositeAppender (in fact copied the AsynchAppender and deleted unnecessary code). DOMConfigurator enhanced: empty class attribute is now expanded to new CompositeAppender. Check, if the childs of a CompositeAppender are all appender-ref. Otherwise continue on the loop like it does on other unresolved children. DOMTestCase enhanced by a new test testComposite(), along with new test resource files input/xml/DOMTestCaseCompositeAppender.xml (based on input/xml/DOMTestCase1.xml), witness/dom.A1.composite (based on witness/dom.A1.1) and witness/dom.A2.1 (based on witness/dom.A2.composite). The testcase nearly succeeded: Only the written stacktraces had two more lines, compared to the witness file. Also the existing tests showed this behaviour. I suppose this is due an inconsistence in my developement environment (I ran the tests within eclipse, JDK 1.4) and not because something is wrong implemented. CodeBase: Trunk, Revision 823021 All my changes are marked with " // CHa Heri Bender (CompositeAppender)" Hope you will enjoy my contribution and add it to the repository. Heri -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
