Skip to content

Your first webservice explained

mythz edited this page Aug 28, 2012 · 11 revisions

Let's look a bit deeper into the Hello World service you created:

As you have seen, the convention for response DTO is {Request DTO Name} + Response. Note, request and response DTO should be in the same namespace if you want ServiceStack to recognize the DTO pair.

To support automatic exception handling, you also need to add a ResponseStatus property to the response DTO:

//Request DTO
public class Hello
{
    public string Name { get; set; }
}

//Response DTO
//Follows naming convention
public class HelloResponse
{
    public ResponseStatus ResponseStatus { get; set; } //Automatic exception handling
    
    public string Result { get; set; }
}

The service implementation you created inherits from IService<>. That's the base interface for all services in ServiceStack.

public class HelloService : IService<Hello>
{
    public object Execute(Hello request)
    {
        return new HelloResponse { Result = "Hello, " + request.Name };
    }
}

There also exists IRestService, but the philosophy for this interface is the same as with IService<T> except that there are specific methods for each HTTP method (GET, POST...). When using IService<T> always the same method will be called, no matter what HTTP method.

ServiceStack provides two base classes which implement these interfaces:

We highly recommend to use one of these two base classes, because they already provide automatic exception handling and add possibilities to access HTTP specific features - without creating a hard dependency to HTTP, so your services still stay highly-reusable/testable even if you use features HTTP provides!

Here's an example of the Hello World service you created using ServiceBase<>:

public class HelloService : ServiceBase<Hello> 
{
   public override object Run(Hello  request)
   {
   	return new HelloResponse { Result = "Hello, " + request.Name };
   }
}

...and RestServiceBase<>:

public class HelloService : RestServiceBase<Hello>
{
    //Called on GET request
    public override object OnGet(Hello request) 
    {
    	return new HelloResponse { Result = "Hello, " + request.Name };
    }
    
    //Called on DELETE request
    public override object OnDelete(Hello request) { ... }
}

Let's look at the AppHost's Configure method:

	      public override void Configure(Container container)
        {
            //register user-defined REST-ful urls
            Routes
              .Add<Hello>("/hello")
              .Add<Hello>("/hello/{Name}");
        }

To register your custom REST URLs, you can also use the RestService attribute on the request DTO instead of Routes.Add in the AppHost:

//Request DTO
[RestService("/hello")]
[RestService("/hello/{Name}")]
public class Hello
{
    public string Name { get; set; }
}

Tip:

[RestService("/hello/{Name}")]

only matches:

  • /hello/name

where as:

[RestService("/hello/{Name*}")]

matches:

  • /hello
  • /hello/name
  • /hello/my/name/is/ServiceStack
  • ...

More details about Routing is explained in this answer on StackOverflow

In the Configure method, you can also access the built-in IoC container and set other application-wide configurations. You can find out more about the IoC container in the next wiki page!

Next wikipage: [[The IoC container]]


  1. Getting Started
    1. Create your first webservice
    2. Your first webservice explained
    3. ServiceStack's new API Design
    4. Designing a REST-ful service with ServiceStack
    5. Example Projects Overview
  2. Reference
    1. Order of Operations
    2. The IoC container
    3. Metadata page
    4. Rest, SOAP & default endpoints
    5. SOAP support
    6. Routing
    7. Service return types
    8. Customize HTTP Responses
    9. Plugins
    10. Validation
    11. Error Handling
    12. Security
    13. Debugging
  3. Clients
    1. Overview
    2. C# client
    3. Silverlight client
    4. JavaScript client
    5. Dart Client
    6. MQ Clients
  4. Formats
    1. Overview
    2. JSON/JSV and XML
    3. ServiceStack's new HTML5 Report Format
    4. ServiceStack's new CSV Format
    5. MessagePack Format
    6. ProtoBuf Format
  5. View Engines 4. Razor & Markdown Razor
    1. Markdown Razor
  6. Hosts
    1. IIS
    2. Self-hosting
    3. Messaging
    4. Mono
  7. Security
    1. Authentication/authorization
    2. Sessions
    3. Restricting Services
  8. Advanced
    1. Configuration options
    2. Access HTTP specific features in services
    3. Logging
    4. Serialization/deserialization
    5. Request/response filters
    6. Filter attributes
    7. Concurrency Model
    8. Built-in caching options
    9. Built-in profiling
    10. Form Hijacking Prevention
    11. Auto-Mapping
    12. HTTP Utils
    13. Virtual File System
    14. Config API
    15. Physical Project Structure
    16. Modularizing Services
    17. MVC Integration
  9. Plugins 3. Request logger 4. Swagger API
  10. Tests
    1. Testing
    2. HowTo write unit/integration tests
  11. Other Languages
    1. FSharp
    2. VB.NET
  12. Use Cases
    1. Single Page Apps
    2. Azure
    3. Logging
    4. Bundling and Minification
    5. NHibernate
  13. Performance
    1. Real world performance
  14. How To
    1. Sending stream to ServiceStack
    2. Setting UserAgent in ServiceStack JsonServiceClient
    3. ServiceStack adding to allowed file extensions
    4. Default web service page how to
  15. Future
    1. Roadmap

Clone this wiki locally