TeaQL now includes two Rust integration modules: teaql-web-integration-axum for request handling and teaql-cache-integration-redis for distributed caching.
Both modules keep infrastructure-specific details behind interfaces that application code can access through its request context.
Optional Redis significantly lowers deployment barriers. Property-level RawSQL increases query flexibility.
+ Redis is now an optional dependency
+ LocalLockService: in-memory lock for non-Redis environments
+ RedisLockService: distributed lock when Redis is available
+ TQLAutoConfiguration: conditionally loads based on classpath
Before: spring-boot-starter-data-redis was mandatory.
After: Works without Redis, automatically falling back to local locks.
@RawSQL("CONCAT(first_name, ' ', last_name)")
String getFullName();
Three levels fully supported: Property-level, Criteria-level, Select-level.
+ Configurable prefix for aggregation result columns
+ Prevents column name conflicts in multi-aggregation queries
Generated Request classes automatically include page and pageSize fields.
String name = Q.user().comment("Query user").purpose("Load data").name().orElse("Unknown");
String email = Q.user().comment("Query user").purpose("Load data").email()
.orElseThrow(() -> new BusinessException("Email required"));
Aligns with Java Optional conventions.
Migrated from Spring Data Redis to Redisson for a richer Redis client experience.
- spring-data-redis RedisTemplate
+ Redisson: RMap, RSet, RLock, etc.
Redisson provides richer distributed data structures, built-in distributed locks, more efficient serialization, and connection pooling.
// Local lock (single JVM)
lockService.acquireLocal("order-process", () -> {
// critical section
});
// Distributed lock (multi-instance)
lockService.acquireDistributed("order-process", () -> {
// critical section across all instances
});
+ LockService interface
+ LocalLockService: ReentrantLock-based
+ DistributedLockService: Redisson-based
+ Configurable lock timeout and retry
The view rendering system gained Redis-backed persistent caching, and the Service Request framework landed.
UserContext now includes DataStore/Redis DataStore:
+ Redis-backed view data storage
+ View parser with template rendering
+ Customizable empty view support
+ Service request controller registry
+ Processor-based request handling
+ Request path prefix configuration
Template renderer for generating UI views from domain models using ObjectMapper for JSON serialization.
viewObject and JsonMe support