Coming soon ChenAIle — agentic microservices: agents, AI tool calls, machine learning and a metrics-driven rules engine Learn more →

Chenile 2.1.33

Prepared October 20, 2026. These notes were written before the 2.1.33 tags were created; the framework repositories were tagged afterward. Check Maven Central and the release process before consuming 2.1.33 from public repositories.

Parent dependency management

Compared with the published 2.1.32 parent, 2.1.33 manages the shared chenile-outbox artifact, replaces crontab-trigger with crontab-api and crontab-service, and removes the retired process-utils artifact. Worker APIs and helpers are consolidated in process-delegate.

Process deployment generation

The chenile-process-management blueprint composes a process server and a headless Kafka worker mini-monolith, with a worker JAR for each definition. Choose an existing registry, a registry colocated with the server (recommended), or a separate registry host. The generated server owns process persistence, triggers, cron schedules and durable outbox dispatch. Workers reach the server through the registry-backed process delegate.

Generated server and worker tests extend KafkaBaseTest and start Kafka through Testcontainers. Docker must be available; a separate Kafka server is unnecessary for these tests. Business worker hooks still require application implementation. See the blueprint reference.

Blueprint composition and validation

Blueprints accept SuperPOM and POM_Dependencies inputs while retaining existing defaults. Aggregation markers support child parameters, repeated expansion and conditional folders. visibleWhen controls conditional input capture.

Fields select declarative rules for Java identifiers, types, packages, project names, versions, HTTP URLs and Kafka topics. The framework validates interactive, file, portal and composed inputs, including nested records, before generation. Existing built-in fields declare the rules their generated code requires. See engine features.

Verification and build fixes

  • All 11 framework repository Maven builds and tests pass at 2.1.33.
  • JGen, STM CLI and the Javadoc aggregation build pass.
  • The process UI passes nine tests and its production build.
  • The HTTP entry point restores a missing ResponseMessage import.
  • The AMQP Event Hubs test emulator no longer reserves unused Kafka port 9092.
  • The Javadoc POM no longer depends on retired process-utils.

JGen defaults and the website’s current version setting now select 2.1.33. Historical feature-version labels remain unchanged.