SchemaValidationException (Jakarta Persistence API documentation)

java.lang.Object
- java.lang.Throwable
- - java.lang.Exception
  - - jakarta.persistence.SchemaValidationException

All Implemented Interfaces:

Serializable
```
public class SchemaValidationException
extends Exception
```
Thrown when schema validation fails.

Since:

3.2

See Also:

SchemaManager.validate(), Serialized Form

Constructor Summary

Constructors
Constructor	Description
`SchemaValidationException(String message, Exception... failures)`	Constructs a new instance with a message and, optionally, an array of exceptions, each representing a problem detected while validating the schema.

Method Summary

All Methods Instance Methods Concrete Methods
Modifier and Type Method Description

Exception[] getFailures()
An array of problems detected while validating the schema.
- Methods inherited from class java.lang.Throwable
  addSuppressed, fillInStackTrace, getCause, getLocalizedMessage, getMessage, getStackTrace, getSuppressed, initCause, printStackTrace, printStackTrace, printStackTrace, setStackTrace, toString
- Methods inherited from class java.lang.Object
  clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait

- Constructor Detail
  - SchemaValidationException
```
public SchemaValidationException(String message,
                                 Exception... failures)
```
    Constructs a new instance with a message and, optionally, an array of exceptions, each representing a problem detected while validating the schema.
    
    Parameters:
    
    message - an overall message
    
    failures - an array of exceptions, each representing a separate problem
- Method Detail
  - getFailures
```
public Exception[] getFailures()
```
    An array of problems detected while validating the schema.
    A persistence provider might choose to fail fast upon encountering a problem with one database object, in which case there is only one problem reported here. Alternatively, a provider might choose to continue validating the remaining database objects, in which case multiple problems might be reported, each as a separate exception instance.