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:

• CON11300: Expanding the reach of the Java ME Platform
• CON5943: Java ME 8 Service Platform

And stay tuned for more in this space!

Cheers,

– Terrence

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:

• CON11300: Expanding the reach of the Java ME Platform
• CON5943: Java ME 8 Service Platform

And stay tuned for more in this space!

Cheers,

– Terrence