LDEV-1697 — Tightened entity resolution for cfc="ns.Name" references: a dotted ref now requires the matching /ns mapping to be declared in the current application. Previously a silent simple-name fallback resolved any registered Name entity regardless of namespace — iteration-order-dependent (happened to pass on Windows, failed on Linux). Unresolvable refs now throw with source CFC and property context: Cannot resolve entity reference [ns.Name] on property [foo] of [...]. Matches ACF behaviour
LDEV-6340 — Entities extending a mappedSuperClass="true" parent no longer log failed to resolve parent entity warnings on every SessionFactory build. Mapped superclasses aren’t entities, so “parent not registered” is the expected state, not an error
LDEV-6342 — Fail fast on three silent-failure sites: HBM file-write errors, a dead catch in AbstractEntityTuplizerImpl, and Dialect registration’s printStackTrace to stderr
LDEV-6343 — generator="foreign" now resolves the id-property type via the relation’s cfc= attribute (parent entity’s id type) instead of silently defaulting to string, fixing FK type mismatch when the parent id is non-string. Misconfigured refs (target CFC not an entity, named property missing, named property not a relation) throw with source context
Changed Edge Case Behavior
** the LDEV-1697 tightening will surface previously-silent misconfigurations where a dotted cfc= ref was relying on the simple-name fallback. If you suddenly hit Cannot resolve entity reference [X.Y] on property [...], declare the missing this.mappings = { "/X" = "..." } in your Application.cfc. This was already failing on Linux (and on ACF), so chances are it was only ever passing on Windows by accident.
This change resolves inconsistent cross platform behaviour and includes a much clearer exception for addressing when encountered.