Java First Verification
Run the shared School SQLite example
from a checkout of teaql-io-site:
npm run verify:school -- --language java
The complete Java application uses the same School
model as the other six runtimes. The runner generates and builds the workspace,
checks root/constant bootstrap twice, saves a school with an audit reason, then
starts a new process to read it back. An independent SQLite checker verifies
persisted fields and relationships after every phase. Logs, exit codes and row
snapshots are retained under artifacts/school/.
Verify the generated application in this order:
- Record the generator, Maven plugin, emitted TeaQL runtime, JDK, framework, and provider versions.
- Build and test the generated library and application without editing generated files.
- Install the generated Runtime Module and invoke context-scoped Ensure Schema explicitly.
- Repeat schema setup and prove root/constant bootstrap is idempotent.
- Execute a bounded generated query with non-empty comment and purpose.
- Create and update a generated entity with an audit reason, then read it back through the provider.
- Exercise Checker/Fix and prove invalid input is rejected before provider mutation.
- Change one model field, regenerate, and review the generated diff.
Use Cross-language Conformance Status for the current evidence vocabulary and the Java Compatibility Archive only to compare historical failure signatures. A successful build is narrower than provider execution; local-source success is narrower than a clean released-package consumer.
Continue with Java Business Scenarios.