Chenile 2.1.34

Tagged October 22, 2026. All 11 framework repositories, chenile-gen, and chenile-javadoc have annotated 2.1.34 tags pushed. chenile-parent:2.1.34 is published on Maven Central. The remaining framework bundles were submitted to Central Publishing and passed validation on October 22; validation does not confirm that every artifact is already indexed in Maven Central. Follow the release process when checking artifact availability. This release builds on 2.1.33 and is a refinement of the process deployment story rather than a new capability area.

Worker failures go to Kafka retry and dead-lettering

A worker — or the callback it makes back to the server — that fails now lets the exception propagate out of the listener, so Chenile Kafka’s consumer applies its bounded retry policy. Once the attempts are exhausted the message lands on a dead-letter topic (default suffix .DLT) instead of blocking the partition or being silently dropped. The server side no longer carries its own Kafka publisher for this path: the server publishes only through the durable outbox, and the worker side owns delivery, retry and dead-lettering. The redundant server-side publication was removed from the generator.

A single shared, concrete worker service

BatchServiceBase (in process-delegate) is now a concrete class, wired once as the shared _processWorkService_ bean in DelegateConfiguration. The generated worker-listener module binds its ProcessWorkListener to that bean rather than to a per-deployment worker service, so the blueprint no longer emits a duplicate service. Every worker in a deployment is served through this one listener.

The chenile-process-worker-set blueprint

Worker-module generation moved into a dedicated, reusable chenile-process-worker-set blueprint. Given a prepared process-definition set it expands one worker module (API + service JAR) per definition, owning the iteration and the process-definition validation. The chenile-process-management blueprint now composes minimonolith with chenile-process-worker-set through a single aggregation marker instead of invoking the per-definition worker blueprint directly.

Header-scoped queue publication

The queue-based process starter now forwards only x--prefixed headers when it publishes a WorkerDto to Kafka — so application and tenant headers such as x-chenile-tenant-id ride along while internal transport properties are dropped.

Verification

• Framework repository Maven builds and tests pass at 2.1.34.
• JGen regenerates the p1 sample deployment with the worker-set blueprint and the shared listener.

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