Exit Print View

Java Platform Micro Edition Software Development Kit Version 3.0

Get PDF Book Print View

Document Information

Getting Started

Java ME Platform SDK Features

Using Sample Projects

Running a Project


Sample Project Overview

Configuring the Web Browser and Proxy Settings

Resolving Reference Problems

Running MIDP and CLDC Sample Projects

Running the Demos Sample Project






Add Stock Symbols to the Ticker

Change the Update Interval

Remove a Stock

Stock Tracker

What If?









Running FPDemo

Running Games

Running Network Demo

Socket Demo

Datagram Demo

Running PhotoAlbum

Running UIDemo

Creating and Editing Projects

Viewing and Editing Project Properties

Running Projects in the Emulator

Searching the WURFL Device Database

Finding Files in the Multiple User Environment

Profiling Applications

Monitoring Network Traffic

Lightweight UI Toolkit

Security and MIDlet Signing

BD-J Support

CLDC Emulation on a Windows Mobile Device

Installing CLDC Emulation on a Windows Mobile Emulator

On-device Debugging

Command Line Reference


JSR Support

JSR 75: PDA Optional Packages

JSR 82: Bluetooth and OBEX Support

JSR 135: Mobile Media API Support

JSR 172: Web Services Support

JSR 177: Smart Card Security (SATSA)

JSR 179: Location API Support

JSRs 184, 226, and 239: Graphics Capabilities

JSR 205: Wireless Messaging API (WMA) Support

JSR 211: Content Handler API (CHAPI)

JSR 238: Mobile Internationalization API (MIA)

JSR 229: Payment API Support

JSR 256: Mobile Sensor API Support


Resolving Reference Problems

Sometimes when you open a project you can see it has a reference warning. In the Projects tab the project name is red, and the icon shows a warning symbol, as seen below:

project with reference problem is shown in red with warning icon

Usually this warning means the project refers to a file or library that cannot be found. Right-click on the project and choose Resolve Reference Problems.

keystore.ks not found in CHAPIDemo with Resolve Reference Problems dialog

The window displays the missing file, the problem, and a possible solution. In this case the project probably used a literal path to the file keystore.ks. Clicking the Resolve... button opens a file browser so you can find the missing file.

Typically the file keystore.ks is stored in installdir\runtimes\cldc-hi-javafx\lib. Locate and select the file. You receive confirmation that the problem is resolved, and you can now click Close.