templates: escape an authored check/guard/unique/refuse message into the Java literal it lands in (#7241)

[iliyan-velichkov]

Cause

#7205 (#7154) introduced JavaLiterals.escape / defaultValueExpression and wired it into exactly one site — the authored dataDefaultValue. Every other authored string the templates write into a Java string literal was still interpolated verbatim, so a " or a \ in one ended that literal and failed javac for the whole generated module, not merely the class carrying the message:

template	literal
template-application-dao-java Repository.java.template	throw new ValidationException("${guard.message}") and the three "${check.message}" document gates
template-application-rest-java Entity{,My,Partner}Controller.java.template	the three row-check "${check.message}" refusals and messages.put("${uniqueConstraint.name}"…, "${uniqueConstraint.message}")
template-application-events-java Generate.java.template	"${itemRefuse} (${fromItemEntity} " + unqualified + ")"

A message in the shape the DSL's own issues suggest — message: 'A "due" date is never before the invoice date' — therefore took every entity of the module down, at publish, in the Problems view, and nothing in the parser refused it.

Change

ModelParameterProcessor already walks the checks it splits into rowChecks / guardChecks / documentChecks; it now puts an escaped twin on each check map (messageJavaLiteral) and on each unique constraint (messageJavaLiteral + nameJavaLiteral), and GlueGenerator does the same for itemRefuse (itemRefuseJavaLiteral). The templates read the twin at the Java sites only — the raw value stays in place for the surfaces that render it as text, which is why the twin was preferred over escaping in place (uniqueConstraint.name is also written into the .schema JSON). A holder carrying no message is left without a twin rather than an empty one, exactly as dataDefaultValueJavaLiteral is: the key's absence is what a template reads.

The .edm XML (escapeXmlText / escapeXml) and the .model JSON (JsonHelper.toJson) already escape these values, so the defect and the fix are confined to the Java emission.

Verification

• mvn -T 1C formatter:validate over the reactor with every formatter-maven-cache.properties deleted first — BUILD SUCCESS.
• mvn -pl components/ide/ide-template -am test — green, including two new ModelParameterProcessorTest cases: one pinning the escaped twins of a row check, a guard, a document check and a unique key (quote and backslash), one pinning that a holder with no message gets no twin.
• IntentEmissionCoverageIT — green. Its fixture now carries a quote in all five families: a document check (itemsMin), a row check (compare), a unique key, a guard and a create-from refuse:. The IT generates, publishes, compiles and runs the module, and asserts both halves: the escaped form in the emitted source, and the authored form in the runtime message the caller is answered with (.body("message", containsString(…)) on the two 400s).
• The pin bites: with the DAO template reverted to ${check.message} the IT fails on the new assertion; restored, it is green again.
• mvn -P release … javadoc build on components/ide/ide-template — BUILD SUCCESS.

Not verified: the rest of the integration suite, and the PostgreSQL leg.

Siblings, not addressed here: #7206 (the .schema JSON), #7207 (JS).

Fixes #7241

🤖 Generated with Claude Code