on on 1139 The Spring.Data assembly provides an implementation of best practice approaches to data access.

Specifically, it contains an abstraction for transaction management that provides the following benefits

    • Provides a consistent programming model across different transaction APIs such as ADO.NET, EnterpriseServices, System.Transactions, and NHibernate.

    • Support for declarative transaction management with any of the above data access technologies

    • Provides a simple API for programmatic transaction management

    • Integrates with Spring's high level persistence integration APIs such as AdoTemplate.

 

Spring.Data also contains an abstraction for data access via ADO.NET that provides the following benefits and features

    • Consistent and comprehensive database provider interfaces for both .NET 1.1 and 2.0

    • Integration with Spring's transaction management features.

    • 'One-liner' implementations for the most common database usage patterns lets you focus on the 'meat' of your ADO.NET code.

    • Template style use of DbCommand that removes the need to write typical ADO.NET boiler-plate code.

    • Easy database parameter creation/management

    • Provider independent exceptions with database error codes and higher level DAO exception hierarchy.

    • Centralized resource management for connections, commands, data readers, etc.

    • Simple DataReader to Object mapping framework.

 

For more information refer to the Getting Started section within this documentation and the reference documentation, the latest copy of which can be found on the Spring.NET web site.

]]> Spring.DataQuickStart are the best places to get started using the functionality contained in Spring.Data.]]> Foundational support for Data Access, providing and ADO.NET Framework, declarative transaction management, and exception translation features. Exception hierarchy enabling sophisticated error handling independent of the data access approach in use.

For example, when DAOs and data access frameworks use the exceptions in this package (and custom subclasses), calling code can detect and handle common problems such as deadlocks without being tied to a particular data access strategy such as ADO.NET or ORM libraries, as well as vendor specific error codes.

]]> Support classes for DAO implementations, providing miscellaneous utility methods. Support classes for generic DAO implementations, providing miscellaneous utility methods. The classes in this package make ADO.NET easier to use and
reduce the likelihood of common errors.

The central class in this namespace is AdoTemplate, which removes the need to manage resource management for connections, commands, data readers, etc. and integrates with Spring's Transaction management features.

]]> Custom schema for DbProvider configuration Provides the core ADO.NET framework, based on AdoTemplate and its associated callback interfaces, delegates and helper objects. Generic implementation of Spring.Data functionality such as AdoTemplate and RowMappers. and stored procedures as thread-safe, reusable objects.

This ADO.NET abstraction depends on the features of AdoTemplate and as such exceptions thrown are in are thrown are within Spring' DAO exception class hierarchy.

]]> Generic implementation of functionality in the Spring.Data.Object namespace. Classes supporting the Spring.Data namespace

Transaction callback interfaces and delegates for use with TransactionTemplate.

Exception hierarchy for Spring's transaction infrastructure,
independent of any specific transaction management system.

]]> Custom schema for configuration of declarative transaction management. Classes supporting the Spring.Transaction namespace.