TeaQL Java Runtime Refactored for Modular Design and Spring Boot Independence
The TeaQL Java runtime (teaql-java) has undergone a significant architectural refactor aimed at three core objectives: enforcing JPMS module boundaries, enabling operation without Spring Boot, and aligning more closely with its Rust counterpart. Previously, all classes resided in flat packages, allowing unrestricted access to internal components like RepositoryAdaptor and GraphMutationEngine. The refactor introduces module-info.java files across runtime modules, sealing internal packages and exposing only what generated code requires. A new TQLResolver interface replaces Spring's ApplicationContext, with a lightweight Map-based implementation supporting non-Spring environments such as plain Java or Android apps. A demo robot-kanban application now runs via a standard main() method using SQLite, validating the framework-agnostic approach.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in