Ottorino Bruni’s Mobile Blog

This article introduces two major enhancements in the Mobile Information Device Profile (MIDP) 3.0 specification, which is currently in Final Draft stage. The two capabilities that will be the foundation of next-generation mobile applications are Inter-MIDlet Communication and Events.

A Summary of MIDP 3.0 Enhancements

As shown in the specification, MIDP 3.0 is expected to provide the following capabilities:

• Enable and specify proper behavior for MIDlets on each of CLDC, CDC, and OSGi, including:
  • Enable multiple concurrent MIDlets
  • Specify proper firewalling, runtime behaviors, and lifecycle management issues for MIDlets
  • Enable background MIDlets (faceless MIDlets with no UI)
  • Enable auto-launched MIDlets (started at device boot time)
  • Enable inter-MIDlet communications (direct communication, and indirect using events)
• Enable shared libraries for MIDlets
• Tighten specifications in all areas to improve cross-device interoperability
• Increase functionality in all areas, including:
  • Improve UI expressability and extensibility
  • Better support for devices with larger displays
  • Enable MIDlets to draw to secondary display(s)
  • Enable richer and higher performance games
  • Secure RMS stores
  • Removable/remote RMS stores
  • IPv6
  • Multiple network interfaces per device
• Specify standard ways for doing MIDlet provisioning through other means, for example, OMA (SyncML) DM/DS, Bluetooth, removable media, MMS, and JSR 232
• Enable extensive device capabilities query
• Enable localization & internationalization (if appropriate, integrating/augmenting JSR 238 as needed)

Now, let’s look into two important capabilities: Inter-MIDlet Communication and Events.

SWFxME is developed by Sajid Ali Anjum (a.k.a SajiSoft) to extend Flash Lite with J2ME (JavaME) via HTTP server (written in J2ME code) and to provide more power to the developer by making a hybrid application. Simply , Flash Lite + J2ME = More Power.

Compatibility

The minimum requirements for SWFxME : Flash Lite 1.1 , MIDP 2.0 , JSR-75 (File Connection API) Support
It should have to work with a phone having these 3 characteristics provided that the platform doesnt have any restrictions to write files, launching files or listening to a local port.

On-device debugging isn’t useful when your MIDlet is running on a client’s phone. This tech tip presents one approach for developers who want a fast and simple way to debug their apps remotely in real environments.

Logging and monitoring your MIDlet in development is easy. Just print some lines on the console around critical events, and you know what is happening within your MIDlet. Integrated development environments (IDEs) such as the NetBeans IDE make this even easier by allowing you to do on-device debugging. But this is of no use to you when your MIDlet is actually being run on a client’s phone.