Viewing and Editing Project Properties
Running Projects in the Emulator
Searching the WURFL Device Database
Finding Files in the Multiple User Environment
CLDC Emulation on a Windows Mobile Device
Installing CLDC Emulation on a Windows Mobile Emulator (Windows Only)
JSR 82: Bluetooth and OBEX Support
JSR 135: Mobile Media API Support
JSR 177: Smart Card Security (SATSA)
JSR 205: Wireless Messaging API (WMA) Support
JSR 211: Content Handler API (CHAPI)
JSR 226: Scalable 2D Vector Graphics
JSR 238: Mobile Internationalization API (MIA)
JSR 256: Mobile Sensor API Support
Each device (or emulator) instance writes its own log into its directory. See Device Names to correlate the directory number and the device name.
Windows
C:\Documents and Settings\user\Application Data\javame-sdk\version\work\emulator-instance\device.logMac OS
/Users/uname/Library/Application Support/javame-sdk/3.0/work/ emulator-instance/device.logThe verbosity of the device instance log is controlled by the log4j.xml file, as described in Device Manager Logs.
A priority value for the categories com.sun or VM can be set to the following levels: ERROR, WARN, INFO, DEBUG, TRACE (ordered from least to most verbose. The verbosity of the device instance log is controlled by log4j.xml, as described in Device Manager Logs.