Thursday Jun 13, 2013

Fresh Bits! Oracle Java ME Embedded 3.3 and ME SDK 3.3 updates

Quick update: 

The Oracle Java ME Embedded 3.3 and Java ME SDK 3.3 EA bits have been refreshed. Please see Terrence Barr's blog for full details.

Thursday Apr 18, 2013

Java ME SDK 3.3 EA and Java ME Embedded 3.3 now available

We are pleased to announce the availability of a number of new releases:
  • Java ME SDK 3.3 EA (Early Access)
  • Java ME Embedded 3.3 for ARM Cortex-M3/M4 (on the KEIL MCBSTM32F200 board)
  • Java ME Embedded 3.3 EA for Raspberry Pi

For more information, please see the Java ME download page, or refer to Terrence Barr's blog.

Note that the Java ME SDK 3.3 is still in Early Access, so you may experience minor issues which are being resolved for the final release.

Thursday Dec 06, 2012

Installing Java ME SDK Plugin for NetBeans is now much easier!

The other day, I wrote about how to download and install Java ME SDK plugin for NetBeans. If you are using NetBeans 7.2.1 or later, you don't have to go through the whole process at all. It's now a matter of a few clicks, because all the plugins are now all in NetBeans update server. Here is a new way to install and integrate Java ME SDK plugins for NetBeans.

1. On NetBeans, go to "Tools"- "Plugins".

2. Click on "Available Plugins" tab. Locate "Java ME SDK Tools".

3. Check the tools you want to install, and click "Install" button at the bottom left corner.

4. NetBeans will restart, and that's it!

Remember that different Java ME SDK requires different version of Plugins.

  • If you are using Java ME SDK 3.0.5 or earlier, you must install Java ME SDK Tool version 2.0 (works with NetBeans 7.1.2 or earlier)
  • If you are using Java ME SDK 3.2 or later, you must install Java ME SDK Tool version 3.0 (works with NetBeans 7.2 or later)

Tuesday Sep 25, 2012

How to integrate Java ME SDK 3.2 with Eclipse

Here is also an instruction on how you can integrate Java ME SDK 3.2 with Eclipse. You need additional steps for Eclipse Juno, because it does automatically detect and download MTJ (Mobile Tools for Java) plugin. The following instruction is for Eclipse Indigo.

1. Download Java ME SDK and Eclipse plugins from here.

2. Install Java ME SDK

3. Launch Eclipse

4. Go to "Help" - "Install New Software"

5. Click "Archive", and choose the Eclipse Plugin zip file you downloaded. Name is something like "Java ME SDK Plugin"

6. Choose Java ME SDK Tools, and select "Next".

7. It will calculate requirements and dependencies. Simply follow the instruction.

8. You may also have to manually install the platform. Check out "Help" - "Preferences" - "Java ME" - "Device Management". If you do not see Java ME SDK 3.2 devices, click "Manual Install" on the right side, and specify the folder where Java ME SDK is installed. By default, it is installed at "C:\Java_ME_platform_SDK_3.2".

9. You're done. Now you can use the Java ME SDK plugins for Eclipse.

How to integrate Java ME SDK 3.2 with NetBeans

Many people like to use Java ME SDK with IDEs. We provided instructions on how to integrate the SDK with NetBeans through the download page, and also through the release note, however, let me explain it here once again with some screen shots.

1. Download Java ME SDK and NetBeans plugin from here.

2. Install Java ME SDK first. You will have the emulator and the runtime on your machine. Also please unarchive the NetBeans plugin somewhere.

3. Launch NetBeans.

4. Go to "Tools" - "Plugins".

5. Check out the "Installed" tab. Check "Show details". If you see the previous version of Java ME SDK Tools installed already. Check those to uninstall them.

6. Go to "Settings" tab.

7. Click "Add", and provide the location of NetBeans plugin. In my case, it is "file:/C:/Users/sungcho/Downloads/nb-me-sdk-plugins-uc/updates.xml". Don't forget to add "updates.xml" at the end.

8. Click "Okay"

9. Click "Available Plugins" tab.

10. If you scroll down, you will see three Java ME SDK Tools. Check "Java ME SDK Tools" plugin. Also check others as you desire.

11. Follow the instruction and install them.

12. Restart NetBeans

13. That is it. Done. Now you will see Oracle Java ME SDK 3.2 in your Java Platform list.

Java ME SDK 3.2 is now live

Hi everyone,

It has been a while since we released the last version. We have been very busy integrating new features and making lots of usability improvements into this new version.

Datasheet is available here. Please visit Java ME SDK 3.2 download page to get the latest and best version yet!

Some of the new features in this version are described below.

Embedded Application Support
Oracle Java ME SDK 3.2 now supports the new Oracle® Java ME Embedded. This includes support for JSR 228, the Information Module Profile-Next Generation API (IMP-NG). You can test and debug applications either on the built-in device emulators or on your device.

Memory Monitor
The Memory Monitor shows memory use as an application runs. It displays a dynamic detailed listing of the memory usage per object in table form, and a graphical representation of the memory use over time.

Eclipse IDE support
Oracle Java ME SDK 3.2 now officially supports Eclipse IDE. Once you install the Java ME SDK plugins on Eclipse, you can start developing, debugging, and profiling your mobile or embedded application.

Skin Creator
With the Custom Device Skin Creator, you can create your own skins. The appearance of the custom skins is generic, but the functionality can be tailored to your own specifications.

 Here are the release highlights.

  • Implementation and support for the new Oracle® Java Wireless Client 3.2 runtime and the Oracle® Java ME Embedded runtime.

    The AMS in the CLDC emulators has a new look and new functionality (Install Application, Manage Certificate Authorities and Output Console).

  • Support for JSR 228, the Information Module Profile-Next Generation API (IMP-NG).

    The IMP-NG platform is implemented as a subset of CLDC. Support includes:

    • A new emulator for headless devices.

    • Javadocs for the following Oracle APIs: Device Access API, Logging API, AMS API, and AccessPoint API.

    • New demos for IMP-NG features can be run on the emulator or on a real device running the Oracle® Java ME Embedded runtime.

  • New Custom Device Skin Creator.

    This tool provides a way to create and manage custom emulator skins. The skin appearance is generic, but the functionality, such as the JSRs supported or the device properties, are up to you. This utility only supported in NetBeans.

  • Eclipse plugin for CLDC/MIDP.

    For the first time Oracle Java ME SDK is available as an Eclipse plugin.

    The Eclipse version does not support CDC, the Memory Monitor, and the Custom Device Skin Creator in this release.

  • All Java ME tools are implemented as NetBeans plugins.

    As of the plugin integrates Java ME utilities into the standard NetBeans menus.

    • Tools > Java ME menu is the place to launch Java ME utilities, including the new Skin Creator.

    • Profile > Java ME is the place to work with the Network Monitor and the Memory Monitor.

    • Use the standard NetBeans tools for debugging.

  • Profiling, Network monitoring, and Memory monitoring are integrated with the NetBeans profiling tools.

    New network monitoring protocols are supported in this release: WMA, SIP, Bluetooth and OBEX, SATSA APDU and JCRMI, and server sockets.

  • Java ME SDK Update Center. Oracle Java ME SDK can be updated or extended by new components. The Update Center can download, install, and uninstall plugins specific to the Java ME SDK. A plugin consists of runtime components and skins.

  • Bug fixes and enhancements.

This version comes with a few known problems. All of them have workarounds, so I hope you don't get stuck in these issues when you are using the product.

  • It you cannot watch static variables during an Eclipse debugging session, and sometimes the Variable view cannot show data.

    In the source code, move the mouse over the required variable to inspect the variable value.

  • A real device shown in the Device Selector is deleted from the Device Manager, yet it still appears.

    Kill the device manager in the system tray, and relaunch it. Then you will see the device removed from the list.

  • On-device profiling does not work on a device.

    CPU profiling, networking monitoring, and memory monitoring do not work on the device, since the device runtime does not yet support it. Please do the profiling with your emulator first, and then test your application on the device.

  • In the Device Selector, using Clean Database on real external device causes a null pointer exception.

    External devices do not have a database recognized by the SDK, so you can disregard this exception message.

  • Suspending the Emulator during a Memory Monitor session hangs the emulator.

    Do not use the Suspend option (F5) while the Memory Monitor is running. If the emulator is hung, open the Windows task manager and stop the emulator process (javaw).

    To switch to another application while the Memory Monitor is running, choose Application > AMS Home (F4), and select a different application.

Please let us know how we can improve it even better, by sending us your feedback.

-Java ME SDK Team

Thursday Apr 26, 2012

Java ME SDK 3.0.5 Known Problems

The following are the known issues and workarounds for Java ME SDK 3.0.5.

  • Java ME SDK 3.0.5 bundled with NetBeans 7.1.1+ might not run on JDK 7 if a proxy is used to connect to the internet.

    In JDK 7, handling of network proxies was re-designed and as a result ME SDK 3.0.5 might not start when installed with JDK 7.

    If you use a proxy to connect to the internet, explicitly add "localhost" and "" as exceptions for the Windows internet connections proxy settings.

  • In rare cases you might have more than one instance of the Java ME SDK 3.0.5 in NetBeans.

    This can happen if:

    • You are running 7.1.1 and you installed the updated plugin before April 2012.

    • You are running 7.1.1 and you circumvented NetBeans autoupdate and manually downloaded and installed a version 3.0.5 plugin.

    To avoid problems with device manager conflicts you must set the Device Manager to use the version installed with 7.1.1.

    1. Select Tools > Java ME > Active Device Manager and choose the version installed in the /mobility directory as the default.

    2. In your Windows System tray, right click on the Device Manager Icon and choose Exit.

    3. Wait for the Device Manager to restart (the icon reappears in the System tray).

  • If both Java ME SDK 3.0 and Java ME SDK 3.0.5 are installed two versions of each emulator are listed when you use the keystore manager to export a keystore file to an emulator. You cannot differentiate which emulator belongs to 3.0 and which belongs to 3.0.5.

    You can export the keystores to both emulators.

  • The Java ME SDK uninstaller does not uninstall plugins from NetBeans.

    In NetBeans, select Tools > Plugins to open the plugins manager and manually uninstall the plugins. In the Installed tab, check the "Show details" box and select the plugins in the category "Java ME SDK Tools", then click the Uninstall button.

  • When using MMAPI you see the message "Unable to create native player".

    Java ME SDK has been pretested with DirectShow filters from the K-Lite Mega Codec Pack version 4.8.0. If creation of an MMAPI player for a particular content type fails, install the corresponding DirectShow filter on the system.

  • Network Monitor seems to hang instead of attaching.

    1. Close the Network Monitor view.

    2. Exit the Device Manager and wait until it is restarted by NetBeans.

    3. To start the Network Monitor for a particular project, right-click the project and select Profile, choose Network Monitor, and select Run.

Friday Mar 30, 2012

Java ME SDK 3.0.5 Integrated with NetBeans 7.1.1

NetBeans 7.1.1 now integrates Java ME SDK 3.0.5, so you do not have to download them separately. Java ME SDK was packaged in NetBeans Mobility Pack, a mobile application development toolkit for NetBeans. Therefore, Java ME SDK is no longer a separate menu on NetBeans.

For those who have not downloaded Java ME SDK yet, please simply visit NetBeans website and download the latest version. For those who already have Java ME SDK integrated with NetBeans 7.1 or earlier, and want to update NetBeans IDE to 7.1.1, don't worry. They can co-exist.

To use NetBeans plug-ins such as Device Selector, profiler, and Internationalization Resource Manager, you have to install "Java ME SDK Tools" from NetBeans. Here is how.

1.  Go to "Tools - Plug-ins" from NetBeans menu. You can find all the plug-ins you can install into NetBeans. Locate "Java ME SDK Tools" from the list.

2. Follow the instruction to install Java ME SDK Plug-ins.

3. Once completed, you will see new menu options. For example, you can find Device Selector under Tools - Java ME. (If you used old version of Java ME, you will notice that there is not 'Java ME' menu any more. This is because all the sub-menus were integrated into appropriate places in NetBeans.)

There is one thing to keep in mind; Since NetBeans 7.1.1 already includes Java ME SDK 3.0.5 and Java ME SDK 3.0.5 plug-ins must be installed through NetBeans plug-in menu, you should not download Java ME SDK 3.0.5 separately and try to integrate it with NetBeans. This may cause issues.

Wednesday Mar 07, 2012

Launching the emulator without specifying jad or jar file name

In version 3.0.5, you can not find an icon to run the SDK from the start menu since we have integrated the SDK with NetBeans. However, if you wondered how you can start the emulator without specifying a device name or jad/jar file name. Here is how.

First, go to the folder where Java ME SDK is installed. From command line, type,

> Emulator  -Xjam

Then you can see the emulator is launched on the screen using the default device skin, "DefaultCldcPhone1". Choose "Application - Run MIDlet Suite" from the menu.

Then you can specify the MIDlet Suite Path either by pasting the full URL, or by clicking "Browse..." button. 

Probably the easiest way to do this is by creating a batch file with this command, create a shortcut to the batch file, and place it wherever you want.


-Java ME SDK Team 

Monday Jan 23, 2012

Eclipse+Java ME SDK Issue

If you have had issues with running your MIDlet in Eclipse + MTJ (Eclipse ME), then this article is relevant to you.

We found out that "Run as emulated MIDlet" option is not supported by Java ME SDK 3.0.5. "Run as emulated MIDlet" means that you are executing a specific MIDlet in the jar file, where jar file contains more than one MIDlet.

Please use "Run as emulated Java ME JAD" option instead. 

Please also let us know if you find any other issues related Eclipse and Java ME SDK.

Friday Dec 30, 2011

Update Java ME SDK through Update Center

We found out that after installing Java ME SDK 3.0.5 plug-ins for NB, you can not run Java SE apps any longer. The issue is fixed now, but you need to update it through update center. Here is a step-by-step guide.

1. Install "Java ME SDK Tools Netbeans Update Site" plugin via ME SDK update center.

2. Restart NetBeans. Now our NB plugins can be updated via standard NetBeans mechanism.

3. Open Netbeans Plugins Center, reload catalog and install update of the NetBeans Plugin.

You are done!

Thank you for using Java ME SDK. 

Wednesday Dec 21, 2011

Multi-language version is released with Update Center

Through usage data analysis, we see that users are all around the world. We would love to support all the languages you are using, but due to the resource constraint, we are supporting two languages other than English - Simplified Chinese and Japanese.

The new release comes with a new feature - update center on NetBeans, where you can download latest plug-ins. You can download Java ME SDK from Oracle Technology Network.

Update Center
Through update center, you can download latest plug-ins for Java ME SDK.

Chinese and Japanese Localization
We offer extensive localization for Chinese and Japanese. They are all in one package.

Friday Dec 16, 2011

Java ME SDK and Eclipse Integration (Video)

For those who prefer watching videos to following instructions in text, we have prepared a video for you. Please follow this Youtube link to watch the video.

How To Integrate Java ME SDK With NetBeans?

Now that you have installed NetBeans and Java ME SDK, but you don't see Java ME SDK menus yet? Probably you have not installed Java ME SDK plugin yet.

After Java ME SDK installation is complete, start your NetBeans to see what happened. You'll notice new 'Java ME' menu up there. It will show only one item "Download JavaME SDK Tools". Plugin download and installation will happen once you press "Yes" button on the corresponding dialog. Be patient, because download takes time. See the progress bar down there. Wait until the Tools are installed, and restart NetBeans. Go to 'Java ME' menu and enjoy the new GUI for Java ME SDK.

font-size: 14px; line-height: 20px; text-align: left; ">Of course, the SDK still can be used via command line interface. The command line tools are in <SDK install dir>\bin. For example, try emulator.exe

How to Uninstall JavaME SDK Plug-in From NetBeans?

Do you need to uninstall Java ME SDK? Have you already integrated it with NetBeans? Since Java ME SDK uninstaller cannot uninstall NetBeans plugin, you have to manually uninstall it once you uninstall Java ME SDK. Many forget this step, and asks us, "I uninstalled Java ME SDK, but I still see it in my NetBeans IDE."

So, how do you uninstall it? The simple answer is, surprisingly, 'like any other NetBeans Plug-in'. Go to the 'Tools' menu in NetBeans, choose 'Plugins', and go the the tab 'Installed'. Make sure the 'Show details' check box up there is checked. Choose the two plugins 'Java ME SDK Tools' and 'Java ME NetBeans Integration' having the Category 'Java ME SDK Tools'. Check them both and press 'Uninstall'.

The only thing left is that the uninstalled SDK 3.0.5 is still registered as one of Java ME Platforms in your NetBeans. Now, you can go to 'Tools' -> Java Platforms and manually delete it from the list of the platforms.


Java ME Platform SDK is a toolbox for developing mobile applications. Java ME SDK Download


« June 2016