servicestack

Is ResponseStatus needed? The wiki says that we need to have a ResponseStatus property in our response DTO to handle exception serialization: https://github.com/ServiceStack/ServiceStack/wiki/Validation However it looks like ResponseStatus is generated automatically even if there is no ResponseStatus property in the response DTO. Do we need the ResponseStatus property? The Error Handling Docs explains how you can control which Services return a populated ResponseStatus DTO, i.e: Error Response Types The Error Response that gets returned when an Exception is thrown varies on whether a

Is it possible, without major hackery, to get the raw request body of a ServiceStack request within the Runner? I am writing an oauth service provider to run on top of ServiceStack using the new API (Service and Runner). Due to how OAuth signing works I need to get the raw request body for each request. The OAuth protection layer is added to the Runner so that an invalid OAuth request can easily return an empty/error response without any boilerplate in the Service class or subclassing a special "OAuthService" class. The way to access the Raw Request Body is to use IHttpRequest.GetRawBody() or

I'm trying to implement a service with Multiple Optional Parameters using ServiceStack.Net At the moment my route looks like this Routes.Add<SaveWeek>("/save/{Year}/{Week}"); I want to support uris like this: /save/2010/12/Monday/4/Tuesday/6/Wednesday/7 ie Monday=4, Tuesday=6 and Wednesday=7 However I want the ability to ignore days i.e. the person calling the service can decide if they want to save each value for each day... i.e. Like this with missing parameter values ?Monday=4&Wednesday=7&Friday=6 Of course one solution would be to have the following route and just pass 0 when I don't want

We have a requirement to upload images using ServiceStack APIs. I am aware of two possible ways: 1) Use JSON object to upload file (Using BASE64 string). 2) Use "multipart/form-data" Is there any other way of uploading files using ServiceStack? Which is better in terms of best practices? The best way to upload files in ServiceStack is to just do a normal HTTP File upload see the source code for imgur.servicestack.net or file uploads in RestFiles for examples. If you don't want to send multipart/form-data then use a binary format like Protocol Buffers support in ServiceStack and send byte[] to

Hi I am new to working with Servicestack and have downloaded their very comprehensive bootstrapapi example and am working with it, but am still having some issues. The issue is with security, what is happening is I am getting 405 errors when trying to access the protected services. Using the authenticate service it appears that I am authenticating correctly. Please help and explain. Here is the code: public class Hello { public string Name { get; set; } } public class AuthHello { public string Name { get; set; } } public class RoleHello { public string Name { get; set; } } public class

I'm trying out the ServiceStack MVC PowerPack, and am trying the included OrmLite ORM and am trying to get data from a table referenced by a foreign key without any idea how to do so. In the OrmLite examples that use the Northwind database, for example, would it be possible to return a Shipper object that included the "ShipperTypeName" as a string looked up through the foreign key "ShipperTypeID"? From http://www.servicestack.net/docs/ormlite/ormlite-overview , I'd like to add the ShipperName field to the Shipper class if possible: [Alias("Shippers")] public class Shipper : IHasId<int> {

I have a POCO like this: public class BlogEntry { public string Title { get; set; } public DateTime Date { get; set; } } Most of the time it's being hydrated from Entity Framework, but it can and will be used outside of Entity Framework. The DateTimeKind for the Date from EF is Unspecified, which from what I read is normal. When I cache this POCO in Redis (using the ServiceStack Redis client), it comes back with a DateTimeKind of Local. So there is a jitter with the returned objects. The first pass (uncached) has ISO-8061 with no offset (DateTimeKind.Unspecified). The second pass (cached) is