using System;
using System.Collections;
using System.Collections.Generic;
using System.Runtime.Serialization;
using ServiceStack;
using ServiceStack.DataAnnotations;
using IDB.API.DTO.Document.Operations;
namespace IDB.API.DTO.Document.Operations
{
public partial class FileExists
{
public virtual string Url { get; set; }
}
public partial class FileExistsResponse
{
public virtual bool Exists { get; set; }
public virtual string Url { get; set; }
public virtual Guid? FileID { get; set; }
public virtual Guid? DocumentID { get; set; }
public virtual int? DocumentQueuedForRegistrationID { get; set; }
}
}
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /xml/reply/FileExists HTTP/1.1
Host: digiofficeapigateway.deltares.nl
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<FileExists xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/IDB.API.DTO.Document.Operations">
<Url>String</Url>
</FileExists>
HTTP/1.1 200 OK Content-Type: application/xml Content-Length: length <FileExistsResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/IDB.API.DTO.Document.Operations"> <DocumentID>00000000-0000-0000-0000-000000000000</DocumentID> <DocumentQueuedForRegistrationID>0</DocumentQueuedForRegistrationID> <Exists>false</Exists> <FileID>00000000-0000-0000-0000-000000000000</FileID> <Url>String</Url> </FileExistsResponse>