What is JBlend™?

• JBlend™ Overview

  Firstly, JBlend™ is the product name for a variety of different versions of JBlend™. The specific version of JBlend™ is typically shown in brackets after JBlend™, such as JBlend™ [micro]. JBlend™[micro] is usually referring to JBlend™ for mobile phones focused on the CLDC/MIDP and CLDC/DoJa markets. JBlend™ is mostly written in the C language, as it must serve as the abstraction layer from the physical platform to the virtual one created by Java. Therefore, JBlend™ must be compiled for each different platform and must be integrated to that platform (sometimes called porting, and sometimes referred to as creating the glue code). As shown below, the standard deliverables include both a binary library for Windows (as part of the Reference Implementation), as well as a binary library for the target system. Example applications are provided, and using the Windows Reference Implementation of JBlend™, the customer can immediately execute these applications. Both the documentation and Windows Reference Implementation provide detailed learning tools for our customers to learn the JBlend™ product.


• Porting Kit

  A kit to help developers embed JBlend™ in a device. It includes the JVM libraries as well as tools and manuals to assist with the process.
  For more information please see the JBlend™ Product Specifications.

• Java Platform

  The software on which a Java application runs. JBlend™ is a Java platform.

• Java Runtime Environment

  In the case of JBlend™[micro], this a generic name for the JVM libraries, the device manufacturer's module and the application management software. Once this environment has been created, Java applications can be executed on the device.

• Device Manufacturer

  Customers that purchase JBlend™ and embed it on their devices.

• Target Devices

  Devices on which JBlend™ is being embedded.

• Device Manufacturer's Module

  The module that a device manufacturer will create in order to embed JBlend™ on a device. This is required to enable access from the Java application to resources in the target device (hardware resources such as the screen or recording media etc).
  The device manufacturer's module must conform to an interface defined by Aplix Corporation. The JVM libraries use this interface to enable the functionality of the Java class libraries.

• JVM Library

  Libraries that implement the JVM and class libraries' functionality. Provided by Aplix Corporation as pre-compiled, linkable libraries. Profiles, optional packages specified by the JSR as well as optional features provided by Aplix Corporation may also be added to the JVM.

• FTT

  JVM acceleration technology developed by Aplix Corporation. Released in 1998. Available for PersonalJava and EmbeddedJava compatible versions of JBlend™.

• FTT3

  An enhanced version of the FTT JVM acceleration technology. Released in 2000. Available for PersonalJava and EmbeddedJava compatible versions of JBlend™.

• KFTT

  JVM acceleration technology developed by Aplix Corporation. Released in 2000. Available for the Java ME CLDC version of JBlend™.

• Reference Implementation (RI)

  An example implementation that can be referred to at the source code level. A reference implementation of the device manufacturer's module implemented for Windows 2000 is provided as part of the JBlend™[micro] porting kit.