Nowadays, it is more and more common for web developers to utilize RESTfull like services in their projects. There is nothing surprising in that, since in the nature of REST is to provide uniform interface to access the data. One may ask, what uniform means at all? Well simply said, all operations have the same meaning
across all the resources they can act on.
OData in turn, is a protocol that exposes your data to the web in a simple, RESTlike manner. A consumer can query the data via set of URL parameters and receive a response in the JSON format, which is native for the web.
Having that in mind, we are happy to announce that forth from Q3 2011 release the navigation controls (for now - RadTreeView, RadMenu, RadListBox, RadComboBox) can be bound to OData services that return JSON feed. After the RadGrid, these are the next portion of controls to support such binding. The binding in turn, can be hierarchical or not. As one may suggest, non-hierarchical controls like the ListBox and the Combo can be bound only to a flat data, whereas the TreeView and the Menu can be bound both against flat and hierarchical data. Let's take a look at the simpler, flat binding first.
We have tried to provide easy and straightforward way to declarative bind a control against OData service. If you take a look at the well known WebService section, you will notice that there is a new nested property available - ODataSettins. And since they say a code block is worth a thousand words, here is one:
If you take a look at the OData sample service metadata document, you will notice a lot in common. This is on purpose. We have tried to mimic the metadata declaration structure as much as possible, so developers already working with OData have easy time when binding RadControls against OData services. On the other hand, we believe that this approach is straightforward and easy to grasp for developers that don't have any experience with OData as well.
Binding to hierarchical data sounds a bit more challenging, fortunately, in this case it is not :) First, lets take a look at a sample JSON returned from OData service:
What you see is an entry of type Category, with the following properties: ID, Name and Products. Apparently, the Products property is marked as "__deferred" and an URL is provided. This is the URL of the related Products, which are going to be accessed on demand. Let's use a TreeView to display that! We have a hierarchy of two levels, on the first level there are the Categories and on the second, the Products for each Category. Here is the needed markup:
Genady Sergeev is a Senior Manager in the Progress Web UI & Tools division, which develops the Kendo UI, UI for ASP.NET MVC and UI for ASP.NET AJAX products. He joined the company back in 2009 and since then he has been involved with the web UI products on a variety of levels, from a single contributor to a senior manager. Genady's main interests are in the field of client-side development and he is a big fan of the DevOps philosophy. In his free time he likes skiing and cross-country cycling.
Copyright © 2016, Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks or appropriate markings.