It might have gone unnoticed to some, but Java ME took a big leap forward a couple of weeks ago with the filing of two new JSRs:
- JSR 360: “Connected Limited Device Configuration 8” (aka CLDC 8)
- JSR 361: “Java ME Embedded Profile” (aka ME EP)
Together, these two JSRs will significantly update, enhance, and modernize the Java ME platform, and specifically small embedded Java, with a host of new features and functionality.
JSR 360 – Connected Limited Device Configuration 8
CLDC 8 is based on JSR 139 (CLDC 1.1) and updates the core Java ME VM, language support, libraries, and features to be aligned with Java SE 8. This will include:
- VM updated to comply with the JVM language specification version 2
- Support for SE 7/8 language features like Generics, Assertions, Annotations, Try-with-Resources, and more
- New libraries such as Collections, NIO subset, Logging API subset
- A consolidated and enhanced Generic Connection Framework for multi-protocol I/O
With CLDC 8, Java ME and Java SE are entering their next phase of alignment – making Java the only technology today that truly scales application development, code re-use, and tooling across the whole range of IT platforms, from small embedded to large enterprise.
JSR 361 – Java ME Embedded Profile
ME EP is based on JSR 228 (IMP-NG) and updates the specification in key areas to provide a powerful and flexible application environment for small embedded Java platforms, building on the features of CLDC 8:
- A new, lightweight component and services model
- Shared libraries
- Multi-application concurrency, inter-application communication, and event system
- Application management
- API optionality, to address low-footprint use cases
With ME EP, application developers will have a modern application environment which allows development and deployment of modular, robust, sophisticated, and footprint-optimized solutions for a wide range of embedded use cases and devices.
Summary
While these JSRs are still under development, it’s clear that there are exciting new times ahead for Java ME – turning into a serious application platform while maintaining the focus on resource-constrained devices to address the expected explosion of small, smart, and connected embedded platforms.
To learn more, click on the above links for JSR 360 and JSR 361. Or review the JavaOne 2012 online presentations on the topic:
Also, for more information on JSR 360, check out Roger Brinkley’s blog “A Look inside JSR 360”.
And stay tuned for more in this space!
Cheers,
— Terrence
9 comments
Comments feed for this article
11/19/2012 at 18:15
Hendy Irawan
Please consider OSGi integration, or simply use it, especially for “A new, lightweight component and services model” …
Why “new” when the existing works just fine and is proven so many years ? Please don’t repeat java.util.logging mistake all over again. 😦
11/19/2012 at 18:28
terrencebarr
Hi Hendy,
OSGi: OSGi R4 is not suitable for resource-constrained devices and has a number of shortcomings (for more info, please see http://tinyurl.com/c46qrs6). We are working with OSGi experts to address this space. Stay tuned.
Cheers,
— Terrence
11/20/2012 at 22:14
Davide
I’m quite excited about this news, I’m glad that something is moving
and I’m quite impressed from CLDC 8.
Do you plan to release JVM for the OSs like Android and Windows Phone?
PS: JavaME SDK 3.2 doesn’t work on Windows 8.
There is no way to launch emulator, neither form netbens neither from Eclipse.
11/20/2012 at 23:02
terrencebarr
Hi Davide,
Currently, Java ME is focused on embedded platforms. There is plenty of opportunity there.
Thanks for the note on ME SDK on Win 8. Will forward it to the product team.
11/27/2012 at 13:36
Davide
I Terrence,
do you know if there is any plan to support JavaME in Windows 8?
Thanks.
11/27/2012 at 17:47
terrencebarr
You mean supporting the ME SDK and the runtime emulation on Windows 8? Yes, that is planned.
11/28/2012 at 11:39
Davide
Yes I mean it, really thanks for your continued support Terrence, I really appreciate it.
07/09/2014 at 06:54
vusi
Is there back-ward compatibility for older j2me devices?
07/17/2014 at 23:02
terrencebarr
Generally, there is backward compatibility with MIDP, but without graphics (LCDUI).