hibernate/hibernate-orm · error · ModelsException

Could not resolve <jdbc-type-name>" + name + "</jdbc-type-na

Error message

Could not resolve <jdbc-type-name>" + name + "</jdbc-type-name>

What it means

Error "Could not resolve <jdbc-type-name>" + name + "</jdbc-type-name>" thrown in hibernate/hibernate-orm.

Source

Thrown at hibernate-core/src/main/java/org/hibernate/boot/models/xml/internal/XmlAnnotationHelper.java:1191

		else if ( jaxbBasicMapping.getJdbcTypeCode() != null ) {
			applyJdbcTypeCode( jaxbBasicMapping.getJdbcTypeCode(), memberDetails, xmlDocumentContext );
		}
		else if ( isNotEmpty( jaxbBasicMapping.getJdbcTypeName() ) ) {
			applyJdbcTypeCode(
					resolveJdbcTypeName( jaxbBasicMapping.getJdbcTypeName() ),
					memberDetails,
					xmlDocumentContext
			);
		}
	}

	private static int resolveJdbcTypeName(String name) {
		try {
			final Field matchingField = SqlTypes.class.getDeclaredField( name );
			return matchingField.getInt( null );
		}
		catch (NoSuchFieldException | IllegalAccessException e) {
			throw new ModelsException( "Could not resolve <jdbc-type-name>" + name + "</jdbc-type-name>", e );
		}
	}

	public static void applyJavaTypeDescriptor(
			String descriptorClassName,
			MutableMemberDetails memberDetails,
			XmlDocumentContext xmlDocumentContext) {
		final JavaTypeAnnotation typeAnn = (JavaTypeAnnotation) memberDetails.applyAnnotationUsage(
				HibernateAnnotations.JAVA_TYPE,
				xmlDocumentContext.getModelBuildingContext()
		);

		final ClassDetails descriptorClass = xmlDocumentContext
				.getModelBuildingContext()
				.getClassDetailsRegistry()
				.resolveClassDetails( descriptorClassName );
		typeAnn.value( descriptorClass.toJavaClass() );
	}

View on GitHub (pinned to fad1729dce)

Solutions

1. Use a registered JDBC type name (see JdbcType registration / standard SQL type codes) in the <jdbc-type-name> element.

Example fix

Use a registered JDBC type name (see JdbcType registration / standard SQL type codes) in the <jdbc-type-name> element.

When it happens

Trigger: An hbm.xml / orm.xml mapping document violates a mapping rule during bootstrap.

Common situations: Legacy XML mappings with invalid combinations (column+formula, mixed inheritance, missing identifiers, bad extends references).

AI-assisted analysis of hibernate/hibernate-orm@fad1729dce (2026-08-22). Data as JSON: /api/errors/1cb1c61ddbcda388. Report an issue: GitHub.