Skip Headers
Oracle® Java Embedded Suite Application Developer's Guide
Release 7.0
  Go To Table Of Contents


3 Application Development

This chapter gives an overview of developing applications with Oracle Java Embedded Suite. For details of working with each component, see Chapter 4, "Working with Oracle Java SE Embedded", Chapter 5, "Working with Java DB", Chapter 6, "Working with GlassFish", and Chapter 7, "Working with Jersey".

Table of Contents

3.1 Application Development Overview

Embedded application development is fundamentally cross-platform work. The target device (platform), on which the application will ultimately be deployed, usually does not have the hardware resources to support advanced development tools. Therefore, you build on a larger host computer, copy the required build artifacts to the target, and debug and tune the application running on the target. Your development environment might include remote execution tools that support debugging and profiling (monitoring memory use) from the host computer.

The method of copying files from the host to the target is highly target- and environment-specific. Options include physically moving a memory card between devices, using scp, and remotely mounting one computer's file system on the other.

3.2 Hybrid Development

The Oracle Java Embedded Suite's JRE is a subset of the full Standard Edition JRE APIs that are included in the JDK. The Java DB, GlassFish, and Jersey components are 100% Java code. Therefore, any application that can run on the target device can run on the host. The host's Java development tools are extensive and integrated. For example, on the host, you can write, run, debug, and profile an application in the NetBeans integrated development environment. There is no need for the target device. You must be sure, however, not to use a JDK API that is not present in the Oracle Java SE Embedded JRE.

3.3 Deploying an Application

You can copy a compiled application's files to any location in the embedded device's file system.

You must launch the application with the Oracle Java Embedded Suite launcher, which by default is deployDir/jes7.0/jre/bin/java. (NetBeans does not support remote launching of Oracle Java Embedded Suite applications.) You must specify the JAR files representing the components the application uses in the launcher's -classpath option. The component chapters in this guide list the JAR files, and you can see sample launch scripts in installDir/jes7.0/samples/dist/run/ (see Chapter 8).

3.4 Modifying Samples

If a sample (see Chapter 8) is usefully close to the design of your application you can clone the $JES_HOME/samples/ directory, delete unwanted samples, and build the desired sample with JDK command line tools or the NetBeans IDE, or an IDE of your choice. Examine the Ant scripts and the launch scripts for hints on building and running an application.