[LOGGING-42] [logging] setUpHandlers leaves handlers null pointer

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.0.4
• Fix Version/s: 1.1.0

Environment

Operating System: All
Platform: All

• Bugzilla Id: 34792
• Assignee: Simon Kitching
• Reporter: ms419
• Created: 07/May/05 11:29
• Updated: 29/Dec/09 16:09
• Resolved: 29/Dec/09 16:09

Description

These errors occur because the "handler" field is null -

[...]
[java] There were 3 errors:
[java] 1)
testSerializable(org.apache.commons.logging.jdk14.CustomConfigTestCase)java.lang.NullPointerException
[java] at
org.apache.commons.logging.jdk14.CustomConfigTestCase.checkLogRecords
(CustomConfigTestCase.java:215)
[java] at
org.apache.commons.logging.jdk14.CustomConfigTestCase.testExceptionMessages
(CustomConfigTestCase.java:139)
[java] at
org.apache.commons.logging.jdk14.CustomConfigTestCase.testSerializable
(CustomConfigTestCase.java:186)
[java] at java.lang.reflect.Method.invoke0 (Method.java)
[java] at java.lang.reflect.Method.invoke (Method.java:255)
[...]

The "handler" field is probably null due to an error in gnu classpath

Anyway, a ClassCastException in setUpHandlers is probably more helpful than
NullPointerExceptions in checkLogRecords -
http://www.sfu.ca/~jdbates/tmp/commons-logging/patch

Thanks for your work on these terrific tools!

Jack