Skip Headers
Dali Java Persistence Tools User Guide
Release 3.2
Release 3.2
  PDF
PDF
Go To Table Of Contents
Contents
Go To Index
Index

Previous
Converting JPA metadata to XML
 
Next
Reference
 

Validating mappings and reporting problems

Errors and warnings on persistent entities and mappings are indicated with a red error or yellow warning next to the resource with the error, as well as the parent containers up to the project.


Tip:

Use the Project Properties page – Errors/Warnings and Java Persistence Preferences page – Errors/Warnings to specify which problems Dali will report.


Figure 3-74 Sample Errors and Warnings

This figure shows sample error and warning icons in the Explorer view.

This section contains information on the following:

Related reference

Related concepts

Error messages

This section contains information on error messages (including how to resolve the issue) you may encounter while working with Dali.

An exception handler class should be specified.

When using a custom exception handler, you must select (or create) a Java class to handle exceptions. See "Customization".

Attribute "<ATTRIBUTE__NAME>" has invalid mapping type in this context

The mapped attribute is invalid. Either change the mapping type or change the entity type.

See "Mapping an entity" for more information.

Attribute "<ATTRIBUTE_NAME>" cannot be resolved.

Dali cannot map the attribute to a database table and column. Verify that you database connection information is correct.

See "Creating a new JPA project" for more information.

Class "<CLASS_NAME>" is not annotated as a persistent class.

The class has not been identified as a persistent class. Configure the class as an Entity, Mapped Superclass, or Embeddable persistent entity.

See "Adding persistence to a class".

Column "<COLUMN_NAME>" cannot be resolved.

You mapped an entity's field to an incorrect or invalid column in the database table. By default, Dali will attempt to map each field in the entity with an identically named row in the database table. If the field's name differs from the row's name, you must explicitly create the mapping.

Map the field to a valid row in the database table as shown in "Mapping an entity".

Converter is unnamed. All converters require a name.

When creating a converter, you must specify its name. See "Converters".

Converter name must not be a reserved converter name.

When creating a converter, you must cannot use the following reserved names:

  • serialized

  • class-instance

  • none

Duplicate class "<CLASS_NAME>".

You created to persistence classes with the same name. Each Java class must have a unique name. See "Adding persistence to a class" for more information.

Entity does not have an Id or Embedded Id.

You created a persistent entity without identifying its primary key. A persistent entity must have a primary key field designated with an @Id or @EmbeddedId annotation.

Add an ID mapping to the entity as shown in "ID mapping" or "Embedded ID mapping".

Multiple generators named "<GENERATOR_NAME>" defined in this persistence unit.

When creating generators, the converter Name must be unique within the persistence unit. See "Primary Key Generation".

Multiple persistence.xml files in project.

You created a JPA project with more than one persistence.xml file. Each JPA project must contain a single persistence.xml file.

See "Managing the persistence.xml file" for more information.

Multiple converters named "<CONVERTER_NAME>" defined in this persistence unit

When creating converters, the converter Name must be unique within the persistence unit. See "Add Converter dialog".

No persistence unit defined.

There is no persistence unit defined in the persistence.xml file. Use the <persistence-unit name="<PERSISTENCE_UNIT_NAME>" tag to define the persistent unit.

See "Managing the orm.xml file" for more information.

No persistence.xml file in project.

You created a JPA project without a persistence.xml file. Each JPA project must contain a single persistence.xml file.

See "Managing the persistence.xml file" for more information.

Property "<PROPERTY_NAME>" will be ignored as shared-cache-mode is set to NONE.

Because the Shared cache mode option is set to NONE, Dali will ignore the property. See "Caching".

Referenced column "<COLUMN_NAME>" in join column "<COLUMN_NAME>" cannot be resolved.

The column that you selected to join a relationship mapping does not exist on the database table. Either select a different column on the Joining Strategy or create the necessary column on the database table.

See "JPA Details view (for attributes)" for more information.

Schema "<SCHEMA_NAME>" cannot be resolved for table/join table "<TABLE_NAME>".

Define the default database schema information in the persistence unit.

See "Managing the orm.xml file" for more information.

Table "<TABLE_NAME>" cannot be resolved.

You associated a persistent entity to an incorrect or invalid database table. By default, Dali will attempt to associate each persistent entity with an identically named database table. If the entity's name differs from the table's name, you must explicitly create the association.

Associate the entity with a valid database table as shown in "Adding persistence to a class".

The @Cache annotation on entity <ENTITY_NAME> has both expiry() and expiryTimeOfDay() specified.

You attempted to include both expiry and expiryTimeOfDay in the @Cache annotation. You may use only one. See"Caching".

The converter class "<CLASS_NAME>" does not exist on the project classpath.

You defined a convert class but did not include the class within the project. See"Converters".

The converter class "<CLASS_NAME>" does not implement the org.eclipse.persistence.mappings.converters.Converter interface

When creating a converter, its class must implement the org.eclipse.persistence.mappings.converters.Converter interface. See"Converters".

The converter class must be defined.

You attempted to use a converter without defining the class. See"Converters".

The entity customizer class "<CLASS_NAME>" does not implement the org.eclipse.persistence.config.DescriptorCustomizer interface.

When using a customer class for an entity, the class must implement the org.eclipse.persistence.config.DescriptorCustomizer interface. See "Advanced"

The exception handler class "<CLASS_NAME>" does not implement the org.eclipse.persistence.exceptions.ExceptionHandler interface.

When using a custom exception handler, you must select (or create) a Java class that implements the org.eclipse.persistence.exceptions.ExceptionHandler class. See "Customization".

The persistent field or property for a Version mapping must be of type int, Integer, short, Short, long, Long, or Timestamp.

Version mappings may be used only with the following attribute types:

  • int

  • Integer

  • short, Short

  • long, Long

  • Timestamp

See "Version mapping".

The struct converter class "<CLASS_NAME>" does not implement the org.eclipse.persistence.platform.database.converters.StructConverter interface.

When creating a Struct converter (to enable custom processing of java.sql.Struct types), its class must implement the org.eclipse.persistence.mappings.converters.StructConverter interface. See"Converters".

Unresolved generator "<GENERATOR_NAME>" is defined in persistence unit.

You created a persistence entity that uses sequencing or a table generator, but did not define the generator in the persistence unit. Either define the generator by using an annotation or including it in the XML mapping file.

Related concepts

Warning messages

This section contains information on warning messages (including how to resolve the issue) you may encounter while working with Dali.

Connection "<CONNECTION_NAME>" is not active. No validation will be done against the data source.

The database connection you specified to use with the JPA project is not active. The JPA project requires an active connection.

No connection specified for the project. No data-specific validation will be performed.

You created a JPA project without specifying a database connection. The JPA project requires an active connection.

See "Creating a new JPA project" or "Modifying persistent project properties" for information on specifying a database connection.

Related concepts