Java Runtime Guide
Java is a Tier 1 TeaQL runtime for enterprise services and the broadest database matrix. It follows the same generated Q, E, Mutation, context, audit, Checker/Fix, Runtime Module, and explicit Ensure Schema contract as the other six runtimes.
Start here
- Java Quick Start — evaluate a model and generate the current Java workspace.
- Java First Verification — verify the generated dependency set, build, startup, query, and audited mutation.
- Java Business Scenarios — find the maintained query, relation, aggregate, expression, and mutation guides.
- Java Customization — extend context and infrastructure without editing generated domain files.
- Java Debugging and Observability — inspect safe SQL evidence, traces, mutation audit, telemetry, and tenant policy.
The detailed Java Runtime Overview explains module and framework boundaries. Use Latest Versions for coordinates and Cross-language Conformance Status for shared capability evidence.
Evidence boundary
Java has broad provider and framework evidence, but a module name or generated target is not a support-lifetime commitment. Verify the exact generated workspace and intended database/framework combination using the Java Compatibility Guide. Older blocked and passing campaigns remain available in the Verification Evidence archive, but do not override the current conformance snapshot.
Learn through an Order
Follow the Order tutorial to download a source-only example, build it with JDK 21/Maven, initialize SQLite and complete your first read and audited quantity/total edit. The package pins published 1.555-RELEASE and includes the generated library and startup code. Continue with bounded pages and expected results in the same tutorial. Use the Order API usage guide for result shapes and the native troubleshooting table for recovery. The coverage matrix keeps remaining writing and clean-machine packaging gaps visible. Existing runtime pending-release and generator-deployment qualifications remain in place.
Compare Java data-access approaches
Evaluating a MyBatis alternative for Java order pages? Start with the mapper/generated-API tradeoffs, then use the qualified native Order tutorial above. The comparison is not a migration-cost or performance benchmark.