Gilhari Autoincrement Example

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.

Gilhari Autoincrement Example

Demonstrates database-generated primary keys (autoincrement IDs) with Gilhari ORM

Gilhari is a Docker-compatible microservice framework that provides RESTful Object-Relational Mapping (ORM) functionality for JSON objects with any relational database.

Remarkably, Gilhari automates REST APIs (POST, GET, PUT, DELETE, etc.) handling, JSON CRUD operations, and database schema setup — no manual coding required.

About This Example

This repository contains a standalone example showing how to configure Gilhari to use database-generated primary keys for JSON objects, eliminating the need for clients to specify ID values.

The example uses the base Gilhari docker image (softwaretree/gilhari) to easily create a new docker image (gilhari_autoincrement_example) that can run as a RESTful microservice (server) to persist app specific JSON objects.

This example can be used standalone as a RESTful microservice or optionally with the ORMCP Server.

Related:

ORMCP Documentation: https://github.com/softwaretree/ormcp-docs
ORMCP/Gilhari Examples: https://github.com/SoftwareTree/ormcp-docs/tree/main/examples - Comprehensive list of examples

Note: This example is also included in the Gilhari SDK distribution. If you have the SDK installed, you can use it directly from the examples/gilhari_autoincrement_example directory without cloning.

Example Overview

The example showcases a JSON object model with one type of object: Employee2 (or JSON_Employee2)

Object Model Overview:

JSON_Employee2: Simple employee object with auto-generated ID
Attributes: id (auto-generated), name, exempt (boolean), compensation (double), DOB (long/milliseconds)
Database Table: Employee2 with column empId for the ID

What Makes This Example Different?

This example is similar to gilhari_simple_example, but with a key difference:

Database-Generated IDs:

The database automatically generates a unique ID (primary key) for each Employee object when inserted
Clients do not need to specify an id value in POST requests
Even if a client specifies an id value, it is ignored by Gilhari
When queried, objects return with their database-assigned IDs

Configuration: See config/gilhari_autoincrement_example.jdx for how to configure autoincrement functionality.

Note: To avoid confusion with other examples, this uses Employee2 or JSON_Employee2 as the container domain model class name.

Employee2 Object Structure

{
  "name": "John Doe",
  "exempt": true,
  "compensation": 75000.00,
  "DOB": 631152000000
}

Note: The id field is not included in POST requests - it's automatically generated by the database. The DOB is represented as milliseconds since epoch (standard for JSON date representation).

After Insertion (with database-assigned ID)

{
  "id": 1,
  "name": "John Doe",
  "exempt": true,
  "compensation": 75000.00,
  "DOB": 631152000000
}

Project Structure

gilhari_autoincrement_example/
├── src/                                 # Container domain model classes
│   └── com/softwaretree/...             # JSON_Employee2.java and base classes
├── config/                              # Configuration files
│   ├── gilhari_autoincrement_example.jdx # ORM specification with autoincrement
│   └── classnames_map_example.json
├── bin/                                 # Compiled .class files
├── scripts/                             # Development scripts
│   └── compile.cmd / .sh                # Compiles the container domain model classes
├── gilhari/                             # Gilhari microservice (Docker) related files
│   ├── Dockerfile                       # Docker image definition
│   ├── gilhari_service.config           # Service configuration
│   ├── build.cmd / .sh                  # Builds the Docker image
│   ├── run_docker_app.cmd / .sh         # Runs the Docker container
│   ├── curlCommands.cmd / .sh           # REST API testing scripts
│   └── connectORMCP.md                  # Connecting ORMCP Server to this microservice
├── kubernetes/                          # Sample Kubernetes deployment
└── sources.txt                          # Generated by scripts/compile (not in Git)

All scripts are meant to be run from the project root directory, for example gilhari\build.cmd (Windows) or ./gilhari/build.sh (Linux/Mac). They also work when started from any other directory.

Source Code

The src directory contains the declarations of the underlying shell (container) classes (e.g., JSON_Employee2) that are used to define the object-relational mapping (ORM) specification for the corresponding conceptual domain-specific JSON object model classes:

JSON_Employee2 class: Simple shell (container) class (.java file) corresponding to the domain-specific JSON object model classes of related entities (Container domain model classes)
JDX_JSONObject: Base class of the container domain model classes for handling persistence of domain-specific JSON objects
Container domain model classes: Only need to define two constructors, with most processing handled by the JDX_JSONObject superclass

Note: Gilhari does not require any explicit programmatic definitions (e.g., ES6 style JavaScript classes) for domain-specific JSON object model classes. It handles the data of domain-specific JSON objects using instances of the container domain model classes and the ORM specification.

Configurations

A declarative ORM specification for the domain-specific JSON object model classes and their attributes is defined in config/gilhari_autoincrement_example.jdx using the container domain model classes. This file defines the mappings between JSON objects and database tables, including the autoincrement configuration for primary keys.

Key points:

Update the database URL and JDBC driver in this file according to your setup
See the JDX_DATABASE and JDBC_DRIVER Specification Guide for configuring different databases
The container domain model classes (like JSON_Employee2) corresponding to the conceptual domain-specific JSON object model classes are defined as subclasses of the JDX_JSONObject class
Appropriate mappings for the domain-specific JSON object model classes are defined in the ORM specification file using the corresponding container domain model classes
Autoincrement configuration tells the database to generate unique IDs automatically

For comprehensive details on defining and using container classes and the ORM specification for JSON object models, refer to the "Persisting JSON Objects" section in the JDX User Manual.

Autoincrement Configuration

The key to this example is in the ORM specification file (config/gilhari_autoincrement_example.jdx), where the primary key is configured to use database autoincrement.

For SQLite (as shown in this example):

SQLMAP FOR id COLUMN_NAME empId SQLTYPE 'INTEGER PRIMARY KEY AUTOINCREMENT'
RDBMS_GENERATED id

For MySQL:

SQLMAP FOR id COLUMN_NAME empId SQLTYPE 'INTEGER AUTO_INCREMENT'
RDBMS_GENERATED id

The RDBMS_GENERATED directive tells Gilhari that the database will generate the ID value.

Docker Configuration

The gilhari/Dockerfile builds a RESTful Gilhari microservice using:

Base Gilhari image (softwaretree/gilhari)
Compiled domain model (.class) files
Configuration files including the ORM specification and a JDBC driver

The Docker build context is the project root, so the ADD paths in the Dockerfile (bin, config, gilhari/gilhari_service.config) are relative to the project root.

Service Configuration

The gilhari/gilhari_service.config file specifies runtime parameters for the RESTful Gilhari microservice:

{
  "gilhari_microservice_name": "gilhari_autoincrement_example",
  "jdx_orm_spec_file": "./config/gilhari_autoincrement_example.jdx",
  "jdbc_driver_path": "/node/node_modules/jdxnode/external_libs/sqlite-jdbc-3.50.3.0.jar",
  "jdx_debug_level": 5,
  "jdx_force_create_schema": "false",
  "jdx_persistent_classes_location": "./bin",
  "classnames_map_file": "config/classnames_map_example.json",
  "gilhari_rest_server_port": 8081
}

The paths in this file (e.g., ./config/..., ./bin) are resolved inside the container, relative to the working directory where the Dockerfile copies bin/ and config/.

Service Configuration Parameters

Parameter	Description	Default
`gilhari_microservice_name`	Optional name to identify this Gilhari microservice. The name is logged on console during start up	-
`jdx_orm_spec_file`	Location of the ORM specification file containing mapping for persistent classes	-
`jdbc_driver_path`	Path to the JDBC driver (.jar) file. SQLite driver included by default	-
`jdx_debug_level`	Debug output level (0-5). 0 = most verbose, 5 = minimal. Level 3 outputs all SQL statements	5
`jdx_force_create_schema`	Whether to recreate database schema on each run. `true` = useful for development, `false` = create only once	false
`jdx_persistent_classes_location`	Root location for compiled persistent (Container domain model) classes. Can be a directory (e.g., ./bin) or a JAR file path. Used as a Java CLASSPATH	-
`classnames_map_file`	Optional JSON file that can map names of container domain model classes to (simpler) object class (type) names (e.g., by omitting a package name) to simplify REST URL	-
`gilhari_rest_server_port`	Port number for the RESTful service. This port number may be mapped to different port number (e.g., 80) by a docker run command.	8081

Build Files

scripts/compile.cmd / scripts/compile.sh: Compiles the container domain model classes
sources.txt: Lists the container domain model class source (.java) files for compilation. The compile script generates it from the .java files under src/, so new classes are picked up automatically
gilhari/build.cmd / gilhari/build.sh: Creates the Gilhari Docker image (gilhari_autoincrement_example) using gilhari/Dockerfile

Note: Compilation targets JDK version 1.8, which is compatible with the current Gilhari version.

Quick Start

For Quick Evaluation (No SDK Required)

If you just want to see this example in action without modifications:

Clone this repository (pre-compiled classes included)
Install Docker
Build and run (skip compilation step)

For Development and Customization

If you want to modify the object model or create your own Gilhari microservices:

Gilhari SDK: Download and install from https://softwaretree.com
JX_HOME environment variable: Set to the root directory of your Gilhari SDK installation
Java Development Kit (JDK 1.8+) for compilation
Docker installed on your system

Note: The Gilhari SDK contains necessary libraries (JARs) and base classes required for compiling container domain model classes. While pre-compiled .class files are included in this repository for immediate use, you'll need the SDK to make any modifications to the object model or to create your own Gilhari microservices.

Build and Run

Option 1: Quick Run (Using Pre-compiled Classes)

Skip compilation and go straight to Docker:

# Windows
gilhari\build.cmd
gilhari\run_docker_app.cmd

# Linux/Mac
./gilhari/build.sh
./gilhari/run_docker_app.sh

Option 2: Compile and Run (For Modifications)

If you've made changes to the source code:

Ensure JX_HOME is set to your Gilhari SDK installation directory (if JX_HOME is not set, the compile script uses ../.., which is the SDK root when this example is in the SDK's examples directory)

Compile the classes:

# Windows
scripts\compile.cmd

# Linux/Mac
./scripts/compile.sh

Build and run the Docker container:

# Windows
gilhari\build.cmd
gilhari\run_docker_app.cmd

# Linux/Mac
./gilhari/build.sh
./gilhari/run_docker_app.sh

REST API Usage

Once running, access the Gilhari microservice at:

http://localhost:<port>/gilhari/v1/:className

Example endpoints:

http://localhost:80/gilhari/v1/Employee2

Supported HTTP Methods

Method	Purpose	Example
GET	Retrieve objects	`GET /gilhari/v1/Employee2`
POST	Create objects (ID auto-generated)	`POST /gilhari/v1/Employee2`
PUT	Update objects	`PUT /gilhari/v1/Employee2`
PATCH	Partial update	`PATCH /gilhari/v1/Employee2`
DELETE	Delete objects	`DELETE /gilhari/v1/Employee2`

Example: Creating an Employee Without Specifying ID

POST Request:

curl -X POST http://localhost:80/gilhari/v1/Employee2 \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Jane Smith",
    "exempt": false,
    "compensation": 68000.00,
    "DOB": 694224000000
  }'

GET Request:

curl -X GET "http://localhost:80/gilhari/v1/Employee2"  \
  -H "Content-Type: application/json"

Response (with database-generated ID):

{
  "id": 1,
  "name": "Jane Smith",
  "exempt": false,
  "compensation": 68000.00,
  "DOB": 694224000000
}

Testing the API

All the curl scripts are in gilhari/. Each one first calls the health/check endpoint and stops with a message if the microservice is not running, and writes the responses to curl.log in the directory it is run from.

Pre-built test scripts:

gilhari/curlCommands.cmd / .sh: Pre-configured REST API test calls demonstrating autoincrement behavior

Other options:

Postman: Import the endpoints for interactive testing
Browser: Access GET endpoints directly
Any REST Client: Standard HTTP methods work with any REST client
ORMCP Server (optional): Use ORMCP Server tools for AI-powered interactions

Using with ORMCP Server (Optional)

This Gilhari microservice can be used with ORMCP Server for AI-powered database interactions. ORMCP Server discovers the object model automatically via the getObjectModelSummary endpoint, so you can query and manipulate Employee2 objects in natural language.

See gilhari/connectORMCP.md for step-by-step setup instructions, including a ready-to-use Claude Desktop configuration and sample prompts.

Development Tools

Docker Container Access

Shell into a running container:

# Find container ID
docker ps

# Access container
docker exec -it <container-id> bash

View Logs

docker logs <container-id>

Stop Container

docker stop <container-id>

Additional Resources

JDX User Manual: "Persisting JSON Objects" section for detailed ORM specification documentation
Gilhari SDK Documentation: The SDK available for download at https://softwaretree.com
ORMCP Documentation: https://github.com/softwaretree/ormcp-docs
Database Configuration Guide: JDX_DATABASE and JDBC_DRIVER Specification Guide
operationDetails Documentation: See the operationDetails Parameter reference in gilhari-docs for GraphQL-like query capabilities
Connecting ORMCP Server: See gilhari/connectORMCP.md

Platform Notes

Script files are provided for both Windows (.cmd) and Linux/Mac (.sh).

Linux/Mac users: Make scripts executable before running:

chmod +x scripts/*.sh gilhari/*.sh

Troubleshooting

Common Issues

Problem: Docker image build fails

Solution: Ensure the base Gilhari image is pulled: docker pull softwaretree/gilhari

Problem: Compilation errors

Solution: Verify JDK 1.8+ is installed and JX_HOME environment variable is set correctly

Problem: Port 80 already in use

Solution: Either stop the service that is already listening on port 80, or change the host port in the gilhari/run_docker_app script (e.g., -p 8080:8081). In the latter case, pass the same port to the curl scripts, for example gilhari\curlCommands.cmd 8080 (Windows) or ./gilhari/curlCommands.sh 8080 (Linux/Mac)

Problem: Database connection errors

Solution: Check config/gilhari_autoincrement_example.jdx for the correct database URL and JDBC driver. The URL is used from inside the Docker container, where localhost refers to the container itself. If your database runs outside the container (on your machine or on another server), specify its host and port in the URL in one of these formats:
```
host.docker.internal:<PortNumber>
<DatabaseServer_IP_Address>:<PortNumber>
```
host.docker.internal refers to the machine running Docker (on Linux, add --add-host=host.docker.internal:host-gateway to the docker run command in gilhari/run_docker_app). See the JDX_DATABASE and JDBC_DRIVER Specification Guide for examples for different databases.

Problem: Changes to the SQLite database are lost when the container is removed, or the microservice should use (and update) the database file in your project

Solution: gilhari/Dockerfile copies the config directory, including the SQLite .db file, into the image, so each container works on its own copy of the database. Changes survive docker stop / docker start but are lost when the container is removed, and they never reach the .db file in your project. To use the original file instead, mount the project's config directory over the container's copy. From the project root, run:
```
# Windows (Command Prompt)
docker run --platform linux/amd64 -p 80:8081 -v "%CD%\config:/opt/gilhari_autoincrement_example/config" gilhari_autoincrement_example:1.0

# Linux/Mac
docker run --platform linux/amd64 -p 80:8081 -v "$(pwd)/config:/opt/gilhari_autoincrement_example/config" gilhari_autoincrement_example:1.0
```
The database URL in the .jdx file (jdbc:sqlite:./config/...) is relative to the container's working directory (/opt/gilhari_autoincrement_example), so it points to the mounted file without any change. Also make sure that jdx_force_create_schema is "false" in gilhari/gilhari_service.config (if you change it, rebuild the image); otherwise the tables are recreated, and their data erased, each time the microservice starts. Keep a backup copy of the .db file, and stop the container before you open or copy the file with other tools.

Problem: IDs are not being auto-generated

Solution: Verify the ORM specification has RDBMS_GENERATED id and proper SQLTYPE for autoincrement (e.g., 'INTEGER PRIMARY KEY AUTOINCREMENT' for SQLite)

Support

For issues or questions:

ORMCP Documentation & Issues: https://github.com/softwaretree/ormcp-docs/issues
This example: https://github.com/SoftwareTree/gilhari_autoincrement_example/issues
Gilhari SDK: Contact support at gilhari_support@softwaretree.com

License

This example code is licensed under the MIT License - see the LICENSE file for details.

Important: This license applies ONLY to the example code in this repository. The Gilhari software (including the softwaretree/gilhari Docker image and Gilhari SDK) and the embedded JDX ORM software are proprietary products owned by Software Tree.

The Gilhari Docker image includes an evaluation license for testing purposes. For production use or licensing beyond the evaluation period, please visit https://www.softwaretree.com or contact gilhari_support@softwaretree.com.

Ready to try it? Start with the Quick Start section above!

Name		Name	Last commit message	Last commit date
bin/com/softwaretree/autoincrementexample/model		bin/com/softwaretree/autoincrementexample/model
config		config
gilhari		gilhari
kubernetes		kubernetes
scripts		scripts
src/com/softwaretree/autoincrementexample/model		src/com/softwaretree/autoincrementexample/model
.dockerignore		.dockerignore
.gitattributes		.gitattributes
.gitignore		.gitignore
LICENSE		LICENSE
README.md		README.md

Navigation Menu

Repository files navigation

Gilhari Autoincrement Example

About This Example

Example Overview

What Makes This Example Different?

Employee2 Object Structure

After Insertion (with database-assigned ID)

Project Structure

Source Code

Configurations

Autoincrement Configuration

Docker Configuration

Service Configuration

Service Configuration Parameters

Build Files

Quick Start

For Quick Evaluation (No SDK Required)

For Development and Customization

Build and Run

Option 1: Quick Run (Using Pre-compiled Classes)

Option 2: Compile and Run (For Modifications)

REST API Usage

Supported HTTP Methods

Example: Creating an Employee Without Specifying ID

Testing the API

Using with ORMCP Server (Optional)

Development Tools

Docker Container Access

View Logs

Stop Container

Additional Resources

Platform Notes

Troubleshooting

Common Issues

Support

License

About

Contributors

Languages

Latest commit

History

Folders and files

Repository files navigation

Gilhari Autoincrement Example

About This Example

Example Overview

What Makes This Example Different?

Employee2 Object Structure

After Insertion (with database-assigned ID)

Project Structure

Source Code

Configurations

Autoincrement Configuration

Docker Configuration

Service Configuration

Service Configuration Parameters

Build Files

Quick Start

For Quick Evaluation (No SDK Required)

For Development and Customization

Build and Run

Option 1: Quick Run (Using Pre-compiled Classes)

Option 2: Compile and Run (For Modifications)

REST API Usage

Supported HTTP Methods

Example: Creating an Employee Without Specifying ID

Testing the API

Using with ORMCP Server (Optional)

Development Tools

Docker Container Access

View Logs

Stop Container

Additional Resources

Platform Notes

Troubleshooting

Common Issues

Support

License

About

Topics

Resources

Stars

Watchers

Forks

Contributors

Languages