Exit Print View

Java Platform Micro Edition Software Development Kit Version 3.0, Mac OS

Get PDF Book Print View
 

Document Information

Getting Started

Features

Using Sample Projects

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

Network Monitoring

Lightweight UI Toolkit

Security and MIDlet Signing

CLDC Emulation on a Windows Mobile Device

Installing CLDC Emulation on a Windows Mobile Emulator (Windows Only)

On-device Debugging

Command Line Reference

Logs

Log Location

Device Manager Logs

Device Instance Logs

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

JSR 180: SIP Communications

JSR 184: Mobile 3D Graphics

JSR 205: Wireless Messaging API (WMA) Support

JSR 211: Content Handler API (CHAPI)

JSR 226: Scalable 2D Vector Graphics

JSR 229: Payment API Support

JSR 238: Mobile Internationalization API (MIA)

JSR 256: Mobile Sensor API Support

Index


Device Instance Logs

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.log

Mac OS

/Users/uname/Library/Application Support/javame-sdk/3.0/work/ emulator-instance/device.log

The 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.