Using Java with Caché Jalapeño
The Jalapeño Persistence Library for Java
[Back] [Next]
   
Server:docs1
Instance:LATEST
User:UnknownUser
 
-
Go to:
Search:    

The Jalapeño Persistence Library for Java is a powerful, lightweight tool that provides an easy way for your Java application to store and access POJOs (Plain Old Java Objects) without mapping.

Many database products and programmer APIs are based on the SQL standard relational model, and require some form of object-relational mapping in order to store and retrieve Java objects. Several standard object-relational mapping frameworks are available (see Using the Caché Hibernate Dialect in Using Caché with JDBC), but they can make a project significantly more complex and harder to maintain.
Jalapeño was designed from the beginning to avoid these problems. It allows you to store POJOs in a database without object-relational mapping, and yet provides easy access to the stored objects with standard, high-performance SQL. The Jalapeño runtime API provides methods that make data storage and retrieval even easier. The object database schema can also be exported to a corresponding relational schema, allowing Jalapeño applications to store and access objects on relational databases.
Jalapeño offers the following benefits:
Installation and Prerequisites
The Jalapeño Persistence Library for Java comes pre-installed as part of the Caché Java binding (see Using Java with Caché). When installing the database server on another system, you have the option to install only the runtime Java components.
This document assumes that you have some knowledge of the following:
Note:
Applications created with versions of Jalapeno earlier than 2012.2 are incompatible with the server for Jalapeno 2012.2 or higher. To update an older application, use Jalapeno 2012.2 or higher to generate new schemas and recompile.
Architecture
The Jalapeño Persistence Library for Java consists of the following components:
The Jalapeño SchemaBuilder is used to create Caché proxy classes (schemas) for a selected set of Java classes. This is effectively the reverse of the standard Caché Java binding architecture (see Using Java with Caché), where Java proxy classes are generated from the original Caché classes.
At runtime, instances of the original POJO classes communicate (using TCP/IP sockets) with corresponding instances of the proxy classes on a Caché server. The following diagram illustrates this structure:
Jalapeño Client/Server Class Architecture
Compare this with the diagram for the standard Java Client/Server Architecture (see Java Binding Architecture in Using Java with Caché).