Note: This file is written in Markdown and is best viewed with a Markdown viewer (e.g., GitHub, GitLab, VS Code, or a dedicated Markdown reader). Viewing it in a plain text editor may not render the formatting as intended.
Copyright (c) 2026 Software Tree
This project demonstrates how JDX ORM supports named sequence generators for creating persistently unique sequence numbers across multiple invocations of an application.
Named sequences are defined declaratively in the ORM mapping file and accessed in application code via the JDXSeqUtil utility class. This allows JDX to automatically generate and assign unique primary key values to new model objects in a controlled and persistent way — meaning sequence counters survive application restarts and continue from where they left off.
The domain model is a simple organizational structure consisting of Departments and Employees, where unique IDs for both are generated using named sequences (DeptIdSequence and EmpIdSequence) rather than being hard-coded or database-auto-incremented.
- Java JDK 8 or higher installed and on the system PATH.
- JDX ORM SDK installed. Set the environment variable
JX_HOMEto the SDK's top-level installation directory. - A supported JDBC-compatible database (MySQL is pre-configured; an SQLite example is also included in the
.jdxfile).
JDX_SequenceExample/
├── config/
│ └── sequence_example.jdx # ORM mapping specification file
├── src/
│ └── com/softwaretree/jdxsequenceexample/
│ ├── SequenceExample.java # Main application entry point
│ └── model/
│ ├── Department.java # Department model class
│ └── Employee.java # Employee model class
├── bin/ # Compiled .class files (generated)
├── sources.txt # List of Java source files for compilation
├── compile.cmd # Windows: compile the Java source files
├── compile.sh # Mac/Linux: compile the Java source files
├── setEnvironment.bat # Windows: sets classpath environment variable
├── setEnvironment.sh # Mac/Linux: sets classpath environment variable
├── runJDXExample.bat # Windows: run the sample application
├── runJDXExample.sh # Mac/Linux: run the sample application
├── forward.bat # Windows: create/recreate the database schema
├── forward.sh # Mac/Linux: create/recreate the database schema
├── JDXDemo.bat # Windows: launch the JDXDemo GUI application
├── JDXDemo.sh # Mac/Linux: launch the JDXDemo GUI application
└── README.md # This file
| Class | Table | Primary Key | Relationships |
|---|---|---|---|
Department |
Dept |
deptId (String) |
None |
Employee |
Emp |
empId (int) |
References Department via deptId |
Both primary keys are assigned using JDX named sequence generators rather than hard-coded values or database auto-increment.
This declarative file defines the object-to-table mappings and the named sequence generators. Key elements:
-
JDX_DATABASEandJDBC_DRIVER— database connection and driver settings. Pre-configured for MySQL; a commented-out SQLite example is also included. -
CLASS/PRIMARY_KEY/RELATIONSHIP— standard class mappings.EmployeereferencesDepartmentviadeptId. -
SEQUENCE— defines named sequence generators:Sequence Name MAX_INCREMENTSTART_WITHDescription EmpIdSequence10 100 Generates employee IDs starting at 100 DeptIdSequence5 (default) Generates department ID sequence numbers MAX_INCREMENTcontrols how many sequence numbers JDX reserves at once from the database, reducing round-trips.START_WITHsets the initial value of the sequence counter.
Refer to the JDX Database & JDBC Driver Specification Guide for configuring other databases.
Note: Update
JDX_DATABASEandJDBC_DRIVERto match your local database setup before running.
Two simple POJOs:
Department— hasdeptId(String) anddeptName(String).Employee— hasempId(int),empName,title,deptId(String), and adeptreference to aDepartmentobject.
Both include a no-arg default constructor as required by JDX ORM.
The entry point of the sample application. It initializes JDX ORM and runs the following sequence:
- Delete all existing
EmployeeandDepartmentobjects from the database. - Create a
JDXSeqUtilforDeptIdSequenceand callgetNextSeq()to obtain a unique department ID, then construct aDepartmentwith ID"DEPT_<seq>"and insert it. - Create a
JDXSeqUtilforEmpIdSequence(with a pre-fetch batch size of 3) and insert fiveEmployeeobjects, each usinggetNextSeq()for theirempId. - Query all employees with a shallow query and print results.
- Retrieve a specific employee (
Charlie) by object ID using a deep query. - Query all departments and print results.
Important note from the code:
JDXSeqUtil.getNextSeq()may internally use a new database transaction to persist the next batch of sequence numbers. It must therefore not be called from within an activeJXSessiontransaction scope (i.e., betweentx_begin()andtx_commit()). This is particularly relevant on Android, which has limitations on concurrent transactions.
Lists all .java source files to be compiled, one per line:
./src/com/softwaretree/jdxsequenceexample/model/Department.java
./src/com/softwaretree/jdxsequenceexample/model/Employee.java
./src/com/softwaretree/jdxsequenceexample/SequenceExample.java
This file is passed to javac using the @sources.txt argument syntax.
Compiles all Java source files listed in sources.txt and outputs .class files into the bin/ directory.
- Requires
JX_HOMEto be set to the JDX ORM SDK installation directory. - Links against
jxclasses.jar(JDX ORM library) andjson-20240303.jar(JSON support). compile.cmd— Windows batch script (supports JDK 8; a commented line supports JDK 9+).compile.sh— Mac/Linux shell script equivalent.
Windows:
compile.cmdMac/Linux:
chmod +x compile.sh # first time only
./compile.shSets the CLASSPATH environment variable to include the JDX ORM libraries and the appropriate JDBC driver JAR for your database. Edit this file to point to the correct JDBC driver for your database before running the application.
setEnvironment.bat— Windows (uses;as classpath separator).setEnvironment.sh— Mac/Linux (uses:as classpath separator; sourced viasource ./setEnvironment.sh).
Invokes the environment setup script to configure the classpath, then runs the SequenceExample main class.
Windows:
runJDXExample.batMac/Linux:
chmod +x runJDXExample.sh # first time only
./runJDXExample.shCreates (or recreates) the database schema based on the ORM specification in the .jdx file, without running the application.
Windows:
forward -createMac/Linux:
chmod +x forward.sh # first time only
./forward.sh -createLaunches the JDXDemo desktop GUI application, which provides a graphical way to browse and interact with the database using the JDX ORM configuration.
Windows:
JDXDemo.batMac/Linux:
chmod +x JDXDemo.sh # first time only
./JDXDemo.sh-
Set
JX_HOMEto the root of your JDX ORM SDK installation. -
Configure the database by editing
config/sequence_example.jdx:- Update
JDX_DATABASEwith the correct connection URL and credentials. - Update
JDBC_DRIVERwith the appropriate JDBC driver class. - Update
setEnvironment.bat(Windows) orsetEnvironment.sh(Mac/Linux) to include the JDBC driver JAR on the classpath.
- Update
-
Compile the source files:
compile.cmd # Windows ./compile.sh # Mac/Linux
-
Run the sample application:
runJDXExample.bat # Windows ./runJDXExample.sh # Mac/Linux
The application will automatically create the database schema on first run (controlled by the
forceCreateSchemaflag inSequenceExample.java).
Mac/Linux tip: Run
chmod +x *.shonce in the project directory to make all shell scripts executable.
This project can be imported directly into the Eclipse IDE as an existing Java project using File → Import → Existing Projects into Workspace.
- JDX Database & JDBC Driver Specification Guide
- JDX ORM SDK documentation (included in your SDK installation under
JX_HOME)