[
https://issues.apache.org/jira/browse/LOGGING-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated LOGGING-42:
-----------------------------------
Fix Version/s: 1.1.0
Assignee: Simon Kitching
> [logging] setUpHandlers leaves handlers null pointer
> ----------------------------------------------------
>
> Key: LOGGING-42
> URL: https://issues.apache.org/jira/browse/LOGGING-42
> Project: Commons Logging
> Issue Type: Bug
> Affects Versions: 1.0.4
> Environment: Operating System: All
> Platform: All
> Reporter: ms419
> Assignee: Simon Kitching
> Fix For: 1.1.0
>
> Attachments: CustomConfigTestCase-patch.txt
>
>
> 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
