Yesterday an update release of Oracle Java Embedded Client (OJEC) 1.1 quietly slipped out door for general availability. Until last year it was pretty difficult to get your hands on either a Connected Limited Device Configuration (CLDC) for small devices or a Connected Device Configuration (CDC) for medium devices java implementation without a substantial initial commitment. But with the the release of OJWC (CLDC) and OJEC (CDC) last year that has changed.
OJEC 1.1 is a binary distribution designed for installation on medium
configurations which is a mid range processor requiring a slow startup time, seamless upgrades, in a cost sensitive hardware environment anywhere from 3.5mb to 8 mb. There are headless as well as headed versions available. It is intended
for
devices,
such
as
Blu--ray
Disc
players,
set--top
boxes,
residential
gateways,VOIP
phones,
and
similar.
From a software point of view, OJEC is
the
Java
runtime
platform
implementation
of
Connected
Device
Configuration
(CDC
v1.1,
JSR--218),
Foundation
Profile
(FP
v1.1,
JSR--219),
and
Personal
Basis
Profile
(PBP
v1.1,
JSR--217) and includes
optional
packages
RMI
(JSR
66),
JDBC
(JSR
169)
and
XML
API
for
Java
ME
(JSR
280),
and
Java
TV
(JSR--927). New to this release is support for the XML API (JSR 280) and a number of
bug fixes and performance enhancements, including an improved
Just-in-Time (JIT) compilation for the x86 chipset architecture. The platforms supported include ArmV5, ArmV6/ArmV7, MIPS 32 74K, and X86 in headless mode.
For embedded developers there are number of advantages to using Java and if you have shied away from the JavaME edition in the past I would encourage you to look into the updated version of OJEC 1.1.
