Skip to main content

Java ME Platform SDK Early Access

Posted by tbrandalik on October 10, 2008 at 2:07 AM PDT

Java ME Platform SDK Early Access has been released yesterday. Have a look at and don't forget to read what's new first, because a lot of cool features is waiting for you. My personal favorites are on-device features. One click on-device deployment and on-device debugging. Who wants to start immediately to discover them just go get and install Java cldc/midp runtime for Windows Mobile shipped with the product.

I'm really happy that ME developers can get an early access to play with it so soon. Let us know what you think, because ... it is still time until final release to add features and improve things. Your feedback is very valuable for us. Looking forward to your comments.


Related Topics >>


Hi, Tomas! I have some (Q)uestions, (S)uggestions and a serious (B)ug: 1.Q) It's possible edit font size (editor)? 2.S) If not is possible "Run in Debug Mode", I suggest remove the icon from Toolbar. 3.S) There are icons that do not change after "Small Toolbar Icons" ("Run in Debug Mode" and "Run Main Project via OTA"). I suggest revision. 4.B) Tools > Java Plataforms > Add Plataform > Java ME MIDP Platform Emulator > NEXT = NullPointerException! Already fixed in Netbeans 6.7 (#157839). Thanks

You will find detailed description if you open Help and go to Cldc Emulation on a Windows Mobile Device -> CLDC Emulator Installation for a device running windows Mobile

How to install the runtime on a windows mobile divice ?

I would like to test Cdc examples from Java ME platform SDK 3.0 on real device. What kind of device I have to use(hardware,os)? And which jvm I need? Thanks.

When can we expect a release for Mac OS X?

Just install the SDK, look and work great. In the past, many have asked for Windows Mobile support, and it is great that it finally arrived. However I like to find out what Java support is there for Windows Mobile (that doesn't seem to have much information on this from the help system) eg mp3, 3d, sms etc. The concept of RecordStore is applicable for less powerful phone, but smartphone is getting more powerful. Is there a more better and flexible persistence system planned (heard one is coming for JavaFX) ? There is also lack of Mp3 audio support among supported medias. Will this be added in final release ? JavaFX mobile support mp3 and so I thought why this SDK yet to explicitly support MP3.

When can we expect a release for Linux?

1. This is on purpose to keep development environment in SDK simple. If users need a full featured IDE for ME development Netbeans Mobility pack is the best choice. We decided to share the same project type which means easy transition to mobility pack.
2. Yes it only supports windows mobile right now , because on device features require built-in support in jvm and only windows mobile devices allow to install jvm. If other device manufacturers want to use on-device features an agent must be incorporated into their jvm. 3. SDK can be integrated into netbeans through platform manager, in the same way as it used to be for wtk 2.5.x. Also Netbeans is necessary if you want to debug. SDK just runs emulator in debug mode it doesn't include debugger. Use Attach debugger from netbeans.

But I am a little bit disappointed: 1. I found it does not support preprocess, like //#ifdef 2. on-device debugging, it seems only support windows mobile device, and I found I could not set break point in the which is is ridiculous! Another question, how can we integrate the SDK into the Netbeans?

C:\Java_ME_platform_SDK_3.0_EA is the default install location. Any reason why this SDK should not reside in Program Files? I question the utility of having the system tray icon for the device manager since the only options are restart and exit. The "device manager" option is constantly grayed out. The data directory is "javeme-sdk" and ".javame-sdk" directly in the users directory. Using UNIX conventions on Windows is really getting old and Sun does it for all its products (Netbeans, this, VirtualBox).

Hi Thomas I've found another bug: Calendar now = Calendar.getInstance(); returns always the 1.1.1970 when I run the Application in the SDK 3.0. Is there any catch or workaround for that?