Conversation
…instead of template name
bechte
requested changes
Jun 15, 2026
bechte
approved these changes
Jun 15, 2026
…teLocale to locale, replace javassist NotFoundException with UnknownIdentifierException
Ole-Ruhl
force-pushed
the
feature/thymeleaf-email-template-backoffice
branch
from
June 15, 2026 10:02
330de1f to
105e304
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Database-driven Thymeleaf email template management
Replaces classpath-based email template resolution with database-stored ThymeleafEmailTemplate items, manageable via
Backoffice or Impex without redeployment.
Changes
Migration
Replace .template(name, locale) call sites with .template(resolvedHtml).templateLocale(locale). Migrate existing
classpath templates to ThymeleafEmailTemplate records via Impex.
I hereby agree to the terms of the CX DEV Tools Contributor License Agreement.