hibernate/hibernate-orm · error · PropertyNotFoundException
Could not resolve PropertyAccess for " + propertyName + " on
Error message
Could not resolve PropertyAccess for " + propertyName + " on " + containerJavaType
What it means
Error "Could not resolve PropertyAccess for " + propertyName + " on " + containerJavaType" thrown in hibernate/hibernate-orm.
Source
Thrown at hibernate-core/src/main/java/org/hibernate/property/access/internal/PropertyAccessStrategyChainedImpl.java:33
public class PropertyAccessStrategyChainedImpl implements PropertyAccessStrategy {
private final PropertyAccessStrategy[] chain;
public PropertyAccessStrategyChainedImpl(PropertyAccessStrategy... chain) {
this.chain = chain;
}
@Override
public PropertyAccess buildPropertyAccess(Class<?> containerJavaType, String propertyName, boolean setterRequired) {
for ( var candidate : chain ) {
try {
return candidate.buildPropertyAccess( containerJavaType, propertyName, true );
}
catch (Exception ignore) {
// ignore
}
}
throw new PropertyNotFoundException( "Could not resolve PropertyAccess for " + propertyName + " on " + containerJavaType );
}
}
View on GitHub (pinned to fad1729dce)
Solutions
- Ensure each element in the chained property path is non-null and resolvable.
- Verify intermediate embeddables/associations in the chain are mapped correctly.
When it happens
Trigger: A name referenced in a mapping, query, or configuration cannot be resolved at runtime.
Common situations: Typos in entity/attribute/mapping names, missing mappings, or refactoring without updating references.
AI-assisted analysis of hibernate/hibernate-orm@fad1729dce (2026-08-22).
Data as JSON: /api/errors/a0e217ac5563cd23.
Report an issue: GitHub.