I'm using Java 6 on Windows XP.
When I open a JOptionPane (see attached source code), it crashes with this exception:
Exception in thread "AWT-EventQueue-0" java.lang.VerifyError: (class: net/sourceforge/napkinlaf/sketch/Template, method: produceXML signature: ()Lorg/jdom/Document;) Incompatible argument to function
at net.sourceforge.napkinlaf.util.NapkinIconFactory.getTemplate(NapkinIconFactory.java:265)
at net.sourceforge.napkinlaf.util.NapkinIconFactory.createSketchedIcon(NapkinIconFactory.java:246)
at net.sourceforge.napkinlaf.NapkinLookAndFeel$13.createValue(NapkinLookAndFeel.java:386)
at javax.swing.UIDefaults.getFromHashtable(Unknown Source)
at javax.swing.UIDefaults.get(Unknown Source)
at javax.swing.MultiUIDefaults.get(Unknown Source)
at javax.swing.UIManager.get(Unknown Source)
at sun.swing.DefaultLookup.get(Unknown Source)
at javax.swing.plaf.basic.BasicOptionPaneUI.getIconForType(Unknown Source)
at javax.swing.plaf.basic.BasicOptionPaneUI.getIcon(Unknown Source)
at javax.swing.plaf.basic.BasicOptionPaneUI.createMessageArea(Unknown Source)
at javax.swing.plaf.basic.BasicOptionPaneUI.installComponents(Unknown Source)
at javax.swing.plaf.basic.BasicOptionPaneUI.installUI(Unknown Source)
at net.sourceforge.napkinlaf.NapkinOptionPaneUI.installUI(NapkinOptionPaneUI.java:22)
at javax.swing.JComponent.setUI(Unknown Source)
at javax.swing.JOptionPane.setUI(Unknown Source)
at javax.swing.JOptionPane.updateUI(Unknown Source)
at javax.swing.JOptionPane.<init>(Unknown Source)
at javax.swing.JOptionPane.showOptionDialog(Unknown Source)
at javax.swing.JOptionPane.showMessageDialog(Unknown Source)
at javax.swing.JOptionPane.showMessageDialog(Unknown Source)
at javax.swing.JOptionPane.showMessageDialog(Unknown Source)
at JOptionPaneTest$1.actionPerformed(JOptionPaneTest.java:23)
...
The same happens when JFileChoosers.
This happens with the 1.0 release as well as with the SVN version of NapkinLAF.
I found the reason. I was using NapkinLAF in my application which was using JDOM 1.0. NapkinLAF expects JDOM 1.1. After upgrading my application to JDOM 1.1, there are no problems anymore.
This bug report can be closed.