[ https://issues.apache.org/jira/browse/JDO-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Bouschen resolved JDO-780. ---------------------------------- Resolution: Fixed Hi Xiangzhe, thanks again for the patch. I checked it in together with some of the formatting changes of your first patch and some refactorings of the code. > Potential NullPointerException in code > -------------------------------------- > > Key: JDO-780 > URL: https://issues.apache.org/jira/browse/JDO-780 > Project: JDO > Issue Type: Bug > Components: tck > Affects Versions: JDO 3.2 > Reporter: XiangzheXu > Assignee: Michael Bouschen > Priority: Major > Labels: NullPointerException > Fix For: JDO 3.2 > > Attachments: new-patch-for-jdo780.patch, patch-for-780.patch > > Original Estimate: 2h > Remaining Estimate: 2h > > In class org.apache.jdo.exectck.Utilities, the method `printClasspath()` > could throw an unexpected NullPointerException. > The related part of that method is shown as follows. > ```java > public void printClasspath() { > ClassLoader loader = ClassLoader.getSystemClassLoader(); > URL[] urls = ((URLClassLoader) loader).getURLs(); > } > ``` > The invocation of `ClassLoader.getSystemClassLoader()` could return null in > JDK 8, as is depicted in the Javadoc in its source code: > @return The system <tt>ClassLoader</tt> for delegation, or > <tt>null</tt> if none > If that is the case, the invocation to `getURLs()` could cause a > NullPointerException. > Maybe we could check for null pointer here or mention the potential > NullPointerException at the Javadoc? -- This message was sent by Atlassian Jira (v8.3.2#803003)