my setting of j2me is eclipse3.1+wtk2.3+eclipseme1.01. but when i is debuging a midlet, eclipse come up an error message:"couldn't connect to virtual machine".and "Debugging not available in OTA mode (Except for -Xjam:run) Warning: Running JAM, Ignoring all other options (but "-Xheapsize", and OTA flags if provided) Running with storage root DefaultColorPhone Running with locale: Chinese_People's Republic of China.936 ** Error installing suite (39): The JAD matches a version of a suite already installed. Execution completed. 245045 bytecodes executed 713 thread switches 890 classes in the system (including system classes) 1529 dynamic objects allocated (63884 bytes) 1 garbage collections (0 bytes collected)" but name of project is same of MIDlet's name.and sometimes ,if i don't press "OK",the MIDlet can run normally.
When you run the MIDlet in the Toolkit are you just running it, or running it in DEBUG mode? Not sure how Eclipse works, but for IntelliJ, I have a DEBUG configuration that connects to a certain port number.
I then run the MIDlet in the Toolkit by selected the debug menu item under the project menu. It pops up an box with the port number that should be used in my debug configuration in IntelliJ. After the MIDlet is running in debug mode, I then run IntelliJ's debug configuration that I created and it connects.
The probleme is that in some cases, exiting from the emulator does not happen correctly and the folder containing the installation of the midlet. there are two possible workarounds: - delete by hand the "<your WTK>\appdb\DefaultColorPhone" folder (mine is at "C:\WTK22\appdb\DefaultColorPhone") - do not exit with the "Exit" menu, but instead use the red button (hangup) on the emulator itself.
Using the "Exit" menu leave the folder "C:\WTK22\appdb\DefaultColorPhone" and prevents the next launch of the emulator to work.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com