Commented Unassigned: OData $batch fails with WCF DS client [1135]

with exception,

Unhandled Exception: System.Data.Services.Client.DataServiceRequestException: An
error occurred while processing this request. ---> System.Data.Services.Client.
DataServiceClientException: <Error><Message>No HTTP resource was found that matc
hes the request URI 'http://localhost:8080/http://localhost:8080/Customers(42)/O
rders'.</Message><MessageDetail>No route data was found for this request.</Messa
geDetail></Error>


I think the problem is in the content-id to uri translation.
Comments: The problem is occurring because the dataservices client formats it sub-request URI's as full URI's, ie: http://localhost:8080/$2/Orders Later, the content id mapping process replaces the content id with the full URI to the new resource: ie: http://localhost:8080/Customers(42) resulting in the invoker trying to execute http://localhost:8080/http://localhost:8080/Customers(42)/Orders I have a work-around that was posted in VB as part of a different problem I am having which Kiren is helping me with. Basically checks for content id's in the URI's during the parse, and makes the URI relative before returning. They appear to be unrelated, but I thought I'd offer my insight. http://stackoverflow.com/questions/17667575/web-api-odata-batch-fails-after-update-to-nightly-build-july-15 Hope it is useful. Steve