Developers creating applications for the Java™ ME environment in Motorola handsets will eventually run into user experience issues once the application they're creating attempts to use sensitive APIs. Those APIs include, but are not limited to JSR 75 – FileConnection, JSR 75 – PIM and JSR 179 – Location. Any application attempting to access these and other sensitive APIs will trigger user-approval prompts every time they are used – unless your application is signed.

While the principle of signing is straightforward, the process can sometimes get complex, especially when working to get an application signed for use on a specific network. Take heart. MOTODEV is here for you, providing practical guidance on signing for mobile developers. If you think your application is ready for prime time, be sure to review MOTODEV's signing document and begin the process of getting development and production certificates today.

Last month, we gave you an overview of the process of deploying a MIDlet to a handset. This month, we're taking a closer look at enabling the KVM Debugging Wire Protocol (KDWP) feature. KDWP is available as a debugging feature on nearly all Motorola handsets, excluding T280, V60, V66 and some flavors of the T720. Traditionally, mobile developers used commands to print lines to the display for verification while MIDlets execute. The KDWP approach gives you hands-on control, allowing you to freeze the MIDlet during execution in the actual handset instead of on an emulator. Using this protocol, you can quickly identify and isolate bugs in your code.

In the March Newsletter, we used the UID tool to enable the Java Application Loader for Motorola handsets. This time, we'll use the UID tool as we enable the KDWP functionality on a handset.

Connect: As before, you'll want to be sure you have a valid and working USB driver for your handset installed on your PC (there are two versions, depending on the handset you're using). Once you've got the connection to your PC established, you can move on to enabling KDWP functionality.

Enable: Connect your handset to your PC, making sure it is recognized and usable by your PC's USB connection. Once you've created a viable connection, download, install and start the UID Extraction tool appropriate for your handset. The UID Extraction tool offers two tabs, one for "UID/IMEI" information and another for "J2ME options." Under J2ME options, you'll find two sections – one for the "Java Application Loader" (JAL) and another for "KDWP." We'll concentrate on KDWP. By default, most Motorola handsets ship with KDWP disabled, but using the UID Extraction tool, enabling it is a snap. First, make sure your handset communicates with the tool by connecting your handset, and waiting for the message "1 device(s) connected" to be displayed at the bottom of the tool window (if you don't see that message, close the UID Extraction tool, disconnect your handset, restart the UID Extraction tool, and reconnect your handset). Once your handset is connected, find "KDWP" as above and click the "Read" button next to the "Current value" field. This will query your handset for its KDWP properties and indicate if KDWP is "Enabled" or "Disabled." If it's "Enabled," you're ready to start debugging. Otherwise, select "Enabled" from the dropdown in the "New Value" field, and click the "Write" button. Now close the UID Extraction Tool. Just like that, you're ready to debug.