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.
NOTE: Datasource can be configured via `Assign datasource` action
Availability
- By default bundled with
- Can be installed with plugin
Jakarta EE: Persistence (JPA), 241.18072
Last modified: 18 June 2024