I have an applet running under Sun's Javasoft jre 1.2.2_p001. Inside this applet we are trying to prompt the user for creating an excel spreadsheet using POI (jakarta-poi-1_5_0-FINAL-bin.zip). We have both the jars (commons-logging- 1.0.jar,jakarta-poi-1_5_0-FINAL.jar) in the javasoft/jre/1.2/lib directory. When attempting to create a new workbook by using new HSSFWorkbook(), we encounter the following error: Exception occurred during event dispatching: java.lang.ExceptionInInitializerError: java.lang.NullPointerException at java.util.Hashtable.get(Unknown Source) at org.apache.commons.logging.LogFactory.getFactory(LogFactory.java, Compiled Code) at org.apache.poi.util.POILogFactory.<clinit>(POILogFactory.java:76) at org.apache.poi.hssf.usermodel.HSSFWorkbook.<clinit> (HSSFWorkbook.java:120) at vsps.iExcel.createWorksheet(iExcel.java:223) at vsps.HorizonExport.<init>(HorizonExport.java, Compiled Code) at app_oca.fQA_SCREEN1.ExportButton_actionPerformed(fQA_SCREEN1.java, Compiled Code) at app_oca.fQA_SCREEN1.actionPerformed(fQA_SCREEN1.java:3287) at vision.vfc.VSImageButtonWithPeer.handleEvent (VSImageButtonWithPeer.java, Compiled Code) at vision.vfc.VSImageButtonWithPeer.mouseReleased (VSImageButtonWithPeer.java:1471) at java.awt.Component.processMouseEvent(Unknown Source) at java.awt.Component.processEvent(Unknown Source) at java.awt.Container.processEvent(Unknown Source) at java.awt.Component.dispatchEventImpl(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEvent(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source) Can you please let me know what could be causing this error and what is the resolution. A prompt response will be greatly appreciated.
I think this have been fixed in 1.5.1 - please attempt to replicate the error there.
The user did not respond. I assume this is a duplicate of a number of logging issues that were fixed in 1.5.1. Users should: 1. Try to test against the head or a recent nightly build to see that bugs have not been resolved 2. At least test against the LATEST version of the production build (meaning if there is a 1.5.1 test there, not 1.5.0)