Uses of Package
org.springframework.dao
Packages that use org.springframework.dao
Package
Description
Exception hierarchy enabling sophisticated error handling independent
of the data access approach in use.
Support classes for DAO implementations,
providing miscellaneous utility methods.
The classes in this package make JDBC easier to use and
reduce the likelihood of common errors.
Provides the core JDBC framework, based on JdbcTemplate
and its associated callback interfaces and helper objects.
JdbcTemplate variant with named parameter support.
Simplification layer for table inserts and stored procedure calls.
Classes supporting the
org.springframework.jdbc.core package.Provides extensible support for initializing databases through scripts.
Provides a strategy for looking up JDBC DataSources by name.
The classes in this package represent RDBMS queries, updates,
and stored procedures as threadsafe, reusable objects.
Support classes for the JDBC framework, used by the classes in the
jdbc.core and jdbc.object packages.
Provides a support framework for incrementing database table values
via sequences, with implementations for various databases.
Abstraction for handling fields of SQLXML data type.
Root package for Spring's O/R Mapping integration classes.
Package providing integration of
Hibernate 5.x
with Spring concepts.
Classes supporting the
org.springframework.orm.hibernate5 package.Package providing integration of JPA (Java Persistence API) with Spring concepts.
Classes supporting the
org.springframework.orm.jpa package.Support classes for adapting to specific JPA vendors.
The classes in this package make R2DBC easier to use and
reduce the likelihood of common errors.
Provides a utility class for easy ConnectionFactory access,
a ReactiveTransactionManager for a single ConnectionFactory,
and various simple ConnectionFactory implementations.
Provides extensible support for initializing databases through scripts.
Provides a strategy for looking up R2DBC ConnectionFactories by name.
Core domain types around DatabaseClient.
Classes providing an abstraction over SQL bind markers.
Support classes for integrating the Spring TestContext Framework
with JUnit 4.12 or higher.
Support classes for integrating the Spring TestContext Framework
with TestNG.
-
Classes in org.springframework.dao used by org.springframework.daoClassDescriptionException thrown on various data access concurrency failures.Root of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.Exception thrown when an attempt to insert or update data results in violation of an integrity constraint.Exception thrown if certain expected data could not be retrieved, e.g.Data access exception thrown when a result was not of the expected size, for example when expecting a single row but getting 0 or more than 1 rows.Root for exceptions thrown when we use a data access resource incorrectly.Root of the hierarchy of data access exceptions that are considered non-transient - where a retry of the same operation would fail unless the cause of the Exception is corrected.Data access exception thrown when a resource fails completely and the failure is permanent.Exception thrown on a pessimistic locking violation.Root of the hierarchy of data access exceptions that are considered transient - where a previously failed operation might be able to succeed when the operation is retried without any intervention by application-level functionality.
-
Classes in org.springframework.dao used by org.springframework.dao.supportClassDescriptionRoot of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.Data access exception thrown when a result was not of the expected size, for example when expecting a single row but getting 0 or more than 1 rows.Exception thrown on mismatch between Java type and database type: for example on an attempt to set an object of the wrong type in an RDBMS column.
-
Classes in org.springframework.dao used by org.springframework.jdbcClassDescriptionRoot of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.Data access exception thrown when a resource fails completely: for example, if we can't connect to a database using JDBC.Exception thrown if certain expected data could not be retrieved, e.g.Data access exception thrown when something unintended appears to have happened with an update, but the transaction hasn't already been rolled back.Root for exceptions thrown when we use a data access resource incorrectly.Root of the hierarchy of data access exceptions that are considered non-transient - where a retry of the same operation would fail unless the cause of the Exception is corrected.Data access exception thrown when a resource fails completely and the failure is permanent.Normal superclass when we can't distinguish anything more specific than "something went wrong with the underlying resource": for example, an SQLException from JDBC we can't pinpoint more precisely.
-
Classes in org.springframework.dao used by org.springframework.jdbc.coreClassDescriptionRoot of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.
-
Classes in org.springframework.dao used by org.springframework.jdbc.core.namedparamClassDescriptionRoot of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.
-
Classes in org.springframework.dao used by org.springframework.jdbc.core.simpleClassDescriptionException thrown on incorrect usage of the API, such as failing to "compile" a query object that needed compilation before execution.
-
Classes in org.springframework.dao used by org.springframework.jdbc.core.supportClassDescriptionRoot of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.
-
Classes in org.springframework.dao used by org.springframework.jdbc.datasource.initClassDescriptionRoot of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.
-
Classes in org.springframework.dao used by org.springframework.jdbc.datasource.lookupClassDescriptionRoot of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.Root of the hierarchy of data access exceptions that are considered non-transient - where a retry of the same operation would fail unless the cause of the Exception is corrected.
-
Classes in org.springframework.dao used by org.springframework.jdbc.objectClassDescriptionRoot of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.Exception thrown on incorrect usage of the API, such as failing to "compile" a query object that needed compilation before execution.
-
Classes in org.springframework.dao used by org.springframework.jdbc.supportClassDescriptionRoot of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.Exception thrown if certain expected data could not be retrieved, e.g.Exception thrown on incorrect usage of the API, such as failing to "compile" a query object that needed compilation before execution.
-
Classes in org.springframework.dao used by org.springframework.jdbc.support.incrementerClassDescriptionRoot of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.
-
Classes in org.springframework.dao used by org.springframework.jdbc.support.xmlClassDescriptionRoot of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.Exception thrown on incorrect usage of the API, such as failing to "compile" a query object that needed compilation before execution.Root of the hierarchy of data access exceptions that are considered non-transient - where a retry of the same operation would fail unless the cause of the Exception is corrected.
-
Classes in org.springframework.dao used by org.springframework.ormClassDescriptionException thrown on various data access concurrency failures.Root of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.Exception thrown if certain expected data could not be retrieved, e.g.Root of the hierarchy of data access exceptions that are considered non-transient - where a retry of the same operation would fail unless the cause of the Exception is corrected.Exception thrown on an optimistic locking violation.Root of the hierarchy of data access exceptions that are considered transient - where a previously failed operation might be able to succeed when the operation is retried without any intervention by application-level functionality.
-
Classes in org.springframework.dao used by org.springframework.orm.hibernate5ClassDescriptionException thrown on various data access concurrency failures.Root of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.Exception thrown if certain expected data could not be retrieved, e.g.Exception thrown on incorrect usage of the API, such as failing to "compile" a query object that needed compilation before execution.Root for exceptions thrown when we use a data access resource incorrectly.Root of the hierarchy of data access exceptions that are considered non-transient - where a retry of the same operation would fail unless the cause of the Exception is corrected.Exception thrown on an optimistic locking violation.Root of the hierarchy of data access exceptions that are considered transient - where a previously failed operation might be able to succeed when the operation is retried without any intervention by application-level functionality.Normal superclass when we can't distinguish anything more specific than "something went wrong with the underlying resource": for example, an SQLException from JDBC we can't pinpoint more precisely.
-
Classes in org.springframework.dao used by org.springframework.orm.hibernate5.supportClassDescriptionRoot of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.Data access exception thrown when a resource fails completely: for example, if we can't connect to a database using JDBC.
-
Classes in org.springframework.dao used by org.springframework.orm.jpaClassDescriptionException thrown on various data access concurrency failures.Root of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.Data access exception thrown when a resource fails completely: for example, if we can't connect to a database using JDBC.Exception thrown if certain expected data could not be retrieved, e.g.Root of the hierarchy of data access exceptions that are considered non-transient - where a retry of the same operation would fail unless the cause of the Exception is corrected.Exception thrown on an optimistic locking violation.Root of the hierarchy of data access exceptions that are considered transient - where a previously failed operation might be able to succeed when the operation is retried without any intervention by application-level functionality.Normal superclass when we can't distinguish anything more specific than "something went wrong with the underlying resource": for example, an SQLException from JDBC we can't pinpoint more precisely.
-
Classes in org.springframework.dao used by org.springframework.orm.jpa.supportClassDescriptionRoot of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.
-
Classes in org.springframework.dao used by org.springframework.orm.jpa.vendorClassDescriptionRoot of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.
-
Classes in org.springframework.dao used by org.springframework.r2dbcClassDescriptionRoot of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.Root for exceptions thrown when we use a data access resource incorrectly.Root of the hierarchy of data access exceptions that are considered non-transient - where a retry of the same operation would fail unless the cause of the Exception is corrected.Normal superclass when we can't distinguish anything more specific than "something went wrong with the underlying resource": for example, an SQLException from JDBC we can't pinpoint more precisely.
-
Classes in org.springframework.dao used by org.springframework.r2dbc.connectionClassDescriptionRoot of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.
-
Classes in org.springframework.dao used by org.springframework.r2dbc.connection.initClassDescriptionRoot of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.
-
Classes in org.springframework.dao used by org.springframework.r2dbc.connection.lookupClassDescriptionRoot of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.Root of the hierarchy of data access exceptions that are considered non-transient - where a retry of the same operation would fail unless the cause of the Exception is corrected.
-
Classes in org.springframework.dao used by org.springframework.r2dbc.coreClassDescriptionRoot of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.
-
Classes in org.springframework.dao used by org.springframework.r2dbc.core.bindingClassDescriptionRoot of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.Root of the hierarchy of data access exceptions that are considered non-transient - where a retry of the same operation would fail unless the cause of the Exception is corrected.
-
Classes in org.springframework.dao used by org.springframework.test.context.junit4ClassDescriptionRoot of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.
-
Classes in org.springframework.dao used by org.springframework.test.context.testngClassDescriptionRoot of the hierarchy of data access exceptions discussed in Expert One-On-One J2EE Design and Development.