This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 136217 - Creating Mobility App from exhisting source, cannot run emulator.
Summary: Creating Mobility App from exhisting source, cannot run emulator.
Status: RESOLVED WORKSFORME
Alias: None
Product: javame
Classification: Unclassified
Component: Build System (show other bugs)
Version: 6.x
Hardware: Other All
: P3 blocker (vote)
Assignee: Petr Suchomel
URL:
Keywords: REGRESSION
Depends on:
Blocks:
 
Reported: 2008-05-31 15:55 UTC by kenh1
Modified: 2008-06-25 10:54 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kenh1 2008-05-31 15:55:08 UTC
I replaced version 5.x and version 6.0 of netbeans with version 6.1 and now cannot run "Mobility Project from Existing 
MIDP Sources". They compile ok, but the emulator will not run. I get the following error message:
Starting emulator in execution mode
com.sun.kvem.midletsuite.InvalidJadException: Reason = 22
The manifest or the application descriptor MUST contain the attribute: MIDlet-1

I am running on Windows Vista
Comment 1 Peter Pis 2008-06-01 00:15:10 UTC
Reassigning to "mobility" for evaluation.
Comment 2 Lukas Hasik 2008-06-02 07:28:39 UTC
it seems that there is no midlet defined in your suite. It was either not defined in the jad or imported in wrong way. 
To fix it go to project properties, in Application descriptor category on MIDlets tab Add... your midlet. If there is a
midlet it should appear in the combo box in the Add midlet dialog.

Questions to find out why it happened:
1, you had 5.5 mobility project and then just opened it in NB 6.1?
2, or did you created new project with ex. sources in 6.1?
Comment 3 Lukas Hasik 2008-06-04 14:17:22 UTC
Have a simple source code of java class. I have this class in a folder and I do the following:
1) Open a New Project
2) Select Mobility Category and "Mobility Project from Existing MIDP Sources". Then click Next.
3) Browse the "Source" files and locate the folder with the source code. Then click Next.
4) Shorten the Project Name to the folder name. Then click Finish.
5) Click "Run Main Project" and you should get the error I experience. 


->The midlet isn't add to JAD automatically. It is up to user to provide JAD that will be used during the import OR she
has to add the midlets to JAD manually 
Comment 4 Lukas Hasik 2008-06-05 08:14:22 UTC
6.0.1 adds all the midlets in sources into JAD automatically when you don't provide the JAD in New File wizard. 
I'm marking this issue as regression.
Comment 5 Petr Suchomel 2008-06-25 10:54:57 UTC
I can not reproduce this issue with current 6.5 build. If you still can reproduce, please attach test case