Note that there are some explanatory texts on larger screens.

plurals
  1. POJava jList NullPointerException error
    text
    copied!<p><strong>Error:</strong></p> <pre><code>Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException at test.factory.MainWindow.setFuncList(MainWindow.java:160) at test.factory.MainWindow.&lt;init&gt;(MainWindow.java:22) at test.factory.MainWindow$2.run(MainWindow.java:151) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251) at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:721) at java.awt.EventQueue.access$200(EventQueue.java:103) at java.awt.EventQueue$3.run(EventQueue.java:682) at java.awt.EventQueue$3.run(EventQueue.java:680) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:76) at java.awt.EventQueue.dispatchEvent(EventQueue.java:691) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:244) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:163) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:151) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:147) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:139) at java.awt.EventDispatchThread.run(EventDispatchThread.java:97) </code></pre> <p><strong>Code:</strong></p> <pre><code>TestFactory tf = new TestFactory(); ArrayList&lt;Function&gt; fList = tf.getFunctions(); DefaultListModel&lt;Function&gt; dFuncList = new DefaultListModel(); fListPane.setModel(dFuncList); for(Function f : fList) { dFuncList.addElement(f); } </code></pre> <hr> <p><strong>Question:</strong></p> <p>Now, if you find the error that's great, but my question is. How do I parse the error text to find where my error originated? I'm used to things like <code>missing ';' at line 24 of C:\filename</code></p> <p><strong>Update:</strong> fList has two elements, so not null.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload