Build: NetBeans IDE 6.5 (Build 200811100001)
VM: Java HotSpot(TM) Client VM, 11.2-b01, Java(TM) SE Runtime Environment, 1.6.0_12-b04
OS: Linux, 2.6.27.12-170.2.5.fc10.i686, i386

User Comments:
lpintilie: I started by creating a project with ktoolbar of WTK2.5.2 without creating any source files - I wanted NB to be my editor for such sources. Later I imported that project in Netbeans. When I created the first Midlet, I used the same name as specified in ktoolbar, but in a different package. When I wanted to correct the details in the NetBeans project, the exception occured, due to conflicting names, I presume. Is this a plausible workflow for developing JavaME applications? Some phone vendors make available their own SDKs, which are in fact rebranded versions of WTK, so having NetBeans use that project structure makes some sense, IMHO.

GUEST: Rename Midlet and setting icon to the midlet application

lpintilie: I started by creating a project with ktoolbar of WTK2.5.2 without creating any source files - I wanted NB to be my editor for such sources. Later I imported that project in Netbeans. When I created the first Midlet, I used the same name as specified in ktoolbar, but in a different package. When I wanted to correct the details in the NetBeans project, the exception occured, due to conflicting names, I presume. Is this a plausible workflow for developing JavaME applications? Some phone vendors make available their own SDKs, which are in fact rebranded versions of WTK, so having NetBeans use that project structure makes some sense, IMHO.



Stacktrace: 
java.lang.NullPointerException
        at org.netbeans.modules.mobility.project.ui.customizer.AddMIDletPanel.isValid(AddMIDletPanel.java:122)
        at java.awt.Component.invalidateIfValid(Component.java:2740)
        at java.awt.Component.setLocale(Component.java:1810)
        at javax.swing.JComponent.<init>(JComponent.java:595)
        at javax.swing.JPanel.<init>(JPanel.java:65)
        at javax.swing.JPanel.<init>(JPanel.java:92)