on on 0 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~Spring.Data.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.

 

]]> The reference documentation and Spring.DataQuickStart are the best places to get started using the functionality contained in Spring.Data. Provides ADO.NET Framework, Data Access Exception Hierarchy and declarative transaction managment. ]]> Support classes for 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 Spring.Data Provides the core ADO.NET framework, based on AdoTemplate and its associated callback interfaces, delegates and helper objects. The classes in this namespace represent RDBMS queries, updates,
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.

]]> Classes supporting the Spring.Data namespace Contains transaction manager, definition, and status interfaces. 

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 declarative transaction management Aspect-Oriented Programming (AOP) based solution for declarative transaction demarcation.  Builds on the AOP infrastructure within Spring.Aop. 

]]> Classes supporting the Spring.Transaction namespace.