A couple of days ago I blogged about the release of a new embedded Java product called “Oracle Java ME Embedded Client”. The interest has been tremendous, and I plan to follow up with more information and a webinar on this topic.
In the meantime, I would like to point your attention to another embedded Java product: Java SE for Embedded. Unlike the Oracle Java ME Embedded Client, which is a Java ME (CDC)-based runtime, the Java SE for Embedded product is a full-blown Java SE 6 runtime, optimized for embedded use in a number of important ways (footprint, memory, power, platform support, and more).
My colleague, Jim Conners, has created an excellent webcast called “Java SE Embedded Development Made Easy”. It consists of two 15-minute video with slides and demos covering all the basics of embedded Java SE development:
- Embedded Microprocessor Trends, covering ARM, Intel, and Freescale
- Getting Started with the SheevaPlug
- The Java SE Embedded Runtime Environment: Downloading and Installing
- Running Apache Tomcat on the SheevaPlug
- Installing and Setting Up NetBeans for Embedded Java Development
- Running the ScoreBoard Application locally and on the SheevaPlug
- Live, Remote Debugging of the ScoreBoard Application
- Monitoring the Remote ScoreBoard Application using JMX and JConsole
Once you’re on Jim’s blog you should also check out his entry “The Unofficial Java SE Embedded SDK”, which talks about using your favorite desktop Java IDE for embedded Java development.
Cheers,
— Terrence
Across the Universe 
4 comments
Comments feed for this article
06/06/2011 at 15:34
Fernando Cassia
I have a radical idea: the disctinction between Java ME and Java SE should be eliminated. Let me explain: there shouldn´t be two different Java VMs to run Java ME or Java SE code.
Java ME has its place as a runtime, and mobile phones should of course use it, but why can´t Java SE run Java ME apps?.
It should be a matter of calling Java SE with the -javame switch. Java SE should also accept signed and unsigned JARs developed for smartphones, and run those with Java -jar appname.jar.
I know there is currently a Java ME emulator that runs on top of Java SE, but it´s overkill.
Just think about it from a market share, not technical perpective… why can´t a set top box with Java SE run Java ME applets designed for smartphones?. A 320×320 Java ME app becomes a quarter-screen widget when run on a 720×480 SD TV screen, or a smaller widget on a HDTV, however, on HD screens the 320×320 applet could be resized up to 2x (think Winamp with the “doublesize” option[1] that rescales everything 2x).
And J2ME apps should run on PCs as desktop widgets! seamlessly!. Think about that!.
FC
PS: What happend to Sun´s plans to create a Java App Store?
[1] Winamp normal size
http://imageshack.us/photo/my-images/716/winampstandardsize.jpg/
Winamp “Double size” trick that rescales bitmaps and app 2x
Double Size:
http://imageshack.us/photo/my-images/232/winampdoublesize.jpg/
08/12/2011 at 10:23
terrencebarr
Fernando,
Sorry for the slow reply. Thanks for the input. We are already investigating ways to bring Java ME and Java SE closer together. I can’t give you specifics but stay tuned – there is more to come on this topic.
Best,
— Terrence
03/07/2012 at 16:02
Michela
Hi Terrence,
It’s possible write a stand-alone java se embedded to work with bluetooth ?
Running in a small device, such as an beagleboard ARM?
Thanks.
03/12/2012 at 12:18
terrencebarr
Bluetooth support depends on the underlying platform/drivers – currently the Java runtime does not support Bluetooth out of the box. However, it is certainly possible to use one of the available Bluetooth modules via serial interface.