Unresolved database references in XML

Reports Persistence ORM XML descriptors that cannot be resolved within the configured datasource and suggests refreshing the datasource or assigning a different one.

Example database table:

  CREATE TABLE DATA_TABLE (
    ID INTEGER,
    DATA VARCHAR(100)
  );

Example JSP file:

  <?xml version="1.0" encoding="UTF-8"?>
  <entity-mappings xmlns="http://java.sun.com/xml/ns/persistence/orm" version="1.0">
    <entity name="JavaEntity" class="JavaEntity">
        <table name="UNKNOWN_TABLE"/> // Error: unresolved table
        <attributes>
          <id name="id">
            <column name="ID" nullable="false"/>
          </id>
          <basic name="UNKNOWN_COLUMN"> // Error: unresolved column
            <column name="UNKNOWN_COLUMN" length="12"/>
          </basic>
        </attributes>
    </entity>
  </entity-mappings>

Locating this inspection

By ID

Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.

JpaDataSourceORMDomInspection

Via Settings dialog

Path to the inspection settings via IntelliJ Platform IDE Settings dialog, when you need to adjust inspection settings directly from your IDE.

Settings or Preferences | Editor | Inspections | JPA

NOTE: Datasource can be configured via `Assign datasource` action

Suppressing Inspection

You can suppress this inspection by placing the following comment marker before the code fragment where you no longer want messages from this inspection to appear:

//noinspection JpaDataSourceORMDomInspection

More detailed instructions as well as other ways and options that you have can be found in the product documentation:

IntelliJ IDEA 2025.2

Inspection Details
By default bundled with:	IntelliJ IDEA 2025.2, Qodana for JVM 2025.2,

Last modified: 18 September 2025