Oracle Product Manager for Java ME SDK, Sungmoon Cho, presented a session, "Developing Java Mobile and Embedded Applications with Java ME SDK 3.2,” wherein he covered the basic new features of the Java ME Platform SDK 3.2, a state-of-the-art toolbox for developing mobile and embedded applications.
The session began with a summary of the four main components of Java ME SDK.
Cho then talked about the Java ME SDK’s on-device tooling architecture:
* Java ME SDK provides an architecture ideal for on-device-debugging.
* Device Manager plays the central role by managing different devices whether it is the emulator or a device that Oracle provides or recommends or a third party device as long as the devices have a Java Runtime that supports the protocol that is designated.
* The Emulator provides an accurate emulation, since it uses the same code base used in Oracle’s Java ME runtime.
* The Universal Emulator Interface (UEI) makes it easy for IDEs to detect the platform.
He then focused on the Java ME SDK release highlights, which include:
* Implementation and support for the new Oracle® Java Wireless Client 3.2 runtime and the Oracle® Java ME Embedded runtime. A full emulation for the runtime is provided.
* Support for JSR 228, the Information Module Profile-Next Generation API (IMP-NG). This is a new profile for embedded devices.
* A new Custom Device Skin Creator.
* An Eclipse plugin for CLDC/MIDP.
* Profiling, Network monitoring, and Memory monitoring are now integrated with the NetBeans profiling tools.
* Java ME SDK Update Center
Cho summarized the main features:
IDE Integration (NetBeans and Eclipse) enables developers to write, run, profile, and debug their applications on their favorite IDE.
This enables developers to more quickly detect the hot spot and where CPU time is being used. They can double click the method to jump directly into the source code.
Developers can monitor objects and memory usage in real time.
Debugger on the Emulator and Device
Developers can run their applications step by step, and inspect the variables to pinpoint the problem. The debugging can take place either on the emulator or the device.
Embedded Application Development
IMP-NG, Device Access, Logging, and AMS API Support are now available.
Connect your device to your computer, and run and debug the application right on your device.
Custom Device Skin Creator
Define your own device and test on an environment that is closest to your target device.
The informative session concluded with a demo that showed more concretely how to apply the new features in Java ME SDK 3.2.