# Frequently Asked Questions

- Verified and Deployed Directories Causing Errors
- Unable to Restore Workbench State
- "KVM Not Ready" when debugging
- Why does my midlet suite have an "Unspecified Platform"?
- Why does Eclipse say my "build path is incomplete"?
- Couldn't get ClassFile object for signature cmd
- "Could not find jar tool executable" When Packaging
- When I try to debug my MIDlet, nothing happens
- When I try to debug my MIDlet in OTA mode, I get an error "No midlets defined in JAD File."

## Verified and Deployed Directories Causing Errors

If the project is used as the source and output folder, trouble can occur with the verified and deployment directories. The Eclipse Java tooling assumes that the verified classes in the the verified directory should be included in the classpath, yet those classes aren't in the appropriate directory structure to match the package name for the class. When this occurs, you may see errors similar to the following snapshot.

If this occurs, it is necessary to define a set of Source Exclusion Patterns to remove the verified and deployed directories from further consideration. Those exclusions may be specified via the project's properties as the following snapshot shows.

As of version 0.4.0 of EclipseME, these exclusions will be automatically added when creating a J2ME Midlet Suite in which the source folder and project folder are the same.

## Unable to Restore Workbench State

This error can occur for numerous reasons, but the most likely reason is the fact that the Platform Components view functionality has migrated to the J2ME preferences. This is a minor error that will only occur once per perspective. See migration information for more details.

## "KVM Not Ready" when debugging

It appears that the WTK Debugger is a combination of Sun's MIDP and K Debug Proxy tools, compiled together into a single executable. Normally, these are two separate tools that talk via a local socket connection. It appears that they still do this and that one half of the conversation is waiting for the other half. This warning appears in the console and does not appear to effect the operation of the debugger against the emulator.

## Why does my midlet suite have an "Unspecified Platform"?

In previous versions of EclipseME, it was very easy to lose the platform definition information associated with a Midlet Suite project. This could cause any number of problems. If this occurs, EclipseME will substitute in the "Unspecified Platform" for your project.

This project does not contain any libraries or other information, so it may also cause your project not to compile. To associate your project with a valid platform definition, use the J2ME Properties.

## Why does Eclipse say my "build path is incomplete"?

There are a number of possible reasons for this. The most likely is a problem with the project's platform definition. See the answer for Why does my midlet suite have an "Unspecified Platform"?

## Couldn't get ClassFile object for signature cmd

This error occurs because Eclipse doesn't currently request class prepare events for all classes. See EclipseME bug 904266 and Eclipse Bug 50531 for further information.

## "Could not find jar tool executable" When Packaging

The process of obfuscated packaging requires that the jar file created by the obfuscation tool must be preverified again. The preverifier tool needs to be able to invoke the jar executable tool while preverifying the jar file from the PATH environment. EclipseME searches for the jar executable within the "Installed Java Runtime Environments" in your Eclipse installation. EclipseME must find at least one full Java Development Kit within the Installed JRE's (a subcategory of the Java category). By default, Eclipse will recognize a JRE rather than a full JDK on Windows. To solve this problem, make sure to point the location of the installed JRE instance to the root directory of the JDK directory. For instance on Windows, that might be something like c:\j2sdk1.4.2.

## When I try to debug my MIDlet, nothing happens

Verify that you made the required changes to the debug settings. For details, see the appropriate section of the installation instructions.

## When I try to debug my MIDlet in OTA mode, I get an error "No midlets defined in JAD File."

You did not define the MIDlet on the Midlets tab of the Application Descriptor. Use the JAD Editor to add an entry for the MIDlet.

This situation can happen when you create your MIDlet class manually, or if you do not have the Add to Application Descriptor option selected when you create the MIDlet as shown in Create a New Midlet