Siphalor/tweed5-commons-logging
1
0
Fork 0
Code Activity

Add better reporting when jdk14 handler setup isn't right.

Browse Source 
git-svn-id: https://svn.apache.org/repos/asf/jakarta/commons/proper/logging/trunk@177867 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Simon Kitching
2005-05-23 01:41:23 +00:00
parent 75c8135c03
commit 195ac37a76
1 changed files with 18 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
src/test/org/apache/commons/logging/jdk14/CustomConfigTestCase.java
View File

@@ -276,10 +276,24 @@ public class CustomConfigTestCase extends DefaultConfigTestCase {
parent = parent.getParent();
}
handlers = parent.getHandlers();
if ((handlers != null) && (handlers.length == 1) &&
(handlers[0] instanceof TestHandler)) {
handler = (TestHandler) handlers[0];
}
// The CustomConfig.properties file explicitly defines one handler class
// to be attached to the root logger, so if it isn't there then
// something is badly wrong...
//
// Yes this testing is also done in testPristineHandlers but
// unfortunately:
// * we need to set up the handlers variable here,
// * we don't want that to be set up incorrectly, as that can
// produce weird error messages in other tests, and
// * we can't rely on testPristineHandlers being the first
// test to run.
// so we need to test things here too.
assertNotNull("No Handlers defined for JDK14 logging", handlers);
assertEquals("Unexpected number of handlers for JDK14 logging", 1, handlers.length);
assertNotNull("Handler is null", handlers[0]);
assertTrue("Handler not of expected type", handlers[0] instanceof TestHandler);
handler = (TestHandler) handlers[0];
}