Right now, we generate a bunch of links in the OData response payloads. These are,
1) Self links - ID, edit and read links.
2) Navigation links,
3) Metadata links.
Customers want to use ODataConventionModelBuilder and yet have a simple way to rebase the links that get generated. Doing it right now involves fixing up these links for each and every entity set and navigation property which is lot of code. Also, the metadata link cannot be changed.
WCF DS supports this scenario. Refer to this blog [post](http://blogs.msdn.com/b/peter_qian/archive/2010/03/24/overwriting-the-service-root-uri-in-wcf-data-service.aspx).
Comments: Unfortunately, the workaround above (custom UrlHelper) does not rewrite next page links as they don't go through the normal UrlHelper.Link generation code path. So, the sample above has added a custom feed serializer to rewrite the next page links before they are written to the response.
1) Self links - ID, edit and read links.
2) Navigation links,
3) Metadata links.
Customers want to use ODataConventionModelBuilder and yet have a simple way to rebase the links that get generated. Doing it right now involves fixing up these links for each and every entity set and navigation property which is lot of code. Also, the metadata link cannot be changed.
WCF DS supports this scenario. Refer to this blog [post](http://blogs.msdn.com/b/peter_qian/archive/2010/03/24/overwriting-the-service-root-uri-in-wcf-data-service.aspx).
Comments: Unfortunately, the workaround above (custom UrlHelper) does not rewrite next page links as they don't go through the normal UrlHelper.Link generation code path. So, the sample above has added a custom feed serializer to rewrite the next page links before they are written to the response.