Telerik OpenAccess Classic

Telerik OpenAccess ORM Send comments on this topic.
Web Services and Telerik OpenAccess ORM
Programmer's Guide > OpenAccess ORM Classic (Old API) > OpenAccess Application Scenarios > Web Services and Telerik OpenAccess ORM

Glossary Item Box

This documentation article is a legacy resource describing the functionality of the deprecated OpenAccess Classic only. The contemporary documentation of Telerik OpenAccess ORM is available here.

Telerik OpenAccess ORM provides a conceptual layer of abstraction over the data source. Telerik OpenAccess ORM materializes data into CLR objects that can be consumed in client applications, such as Windows Forms applications and ASP.NET applications. Telerik OpenAccess ORM supports serialization of objects into formats that enable remote and message-based exchange of persistent classes, such as Web services and the Windows Communication Foundation (WCF). Objects can be serialized using binary serialization, XML serialization, and WCF contract serialization for transport using binary stream or message-based protocols.

ADO.NET Data Services also enables you to provide dynamic access to Telerik OpenAccess ORM tool in an XML format that can be used by applications. This data is accessed by using standard Representational State Transfer (REST) HTTP actions, such as GET, PUT, and POST. For more information, see ADO.NET Data Services Framework.

The following should be considered when creating Web services or WCF services that use the Telerik OpenAccess ORM tool:

  • Full-graph serialization is supported for binary serialization and DataContract serialization. XML serialization does not serialize related objects.
  • You may need to attach or add the object to an Object Scope, or you may just want to apply property changes to the original object.
  • Stateless services are recommended. Services should be designed such that an object scope is only maintained for the duration of a request or a response. The message exchange pattern should include enough information so that changes can be applied without having to persist objects or re-query the data source to retrieve the original object.


You can find more Application Scenarios here.