I'm using DD4T and have some XML being generated which I can now query from the OData service. Unfortunately the DD4T content comes back serialised into the
content property of the response.
This links back to the question I asked on connecting the two aspects of DD4T - the CM side sticks out XML into the broker, which is fine... but I want some way of creating a loosely coupled platform independent way of retrieving the right content on a URI request to a REST service, meaning MV* patterns can be employed without any dependency on a language.
URL requested - http://test.site/Home/Index
Request routed to a service which then takes over the DD4T function and can sort out the response to the client, with complete component link resolution, into some arbritary data format (JSON in my case)
Rob Stevenson-Leggett kindly provided the link to the OData service provider from DD4T->TCDS - I'm presuming DD4T on the web application side hasn't been RESTified up yet by anyone?