问题描述

我正在使用 ServiceStack 将一些对象序列化和反序列化为 JSON.考虑这个例子:

I'm using ServiceStack to serialize and deserialize some objects to JSON. Consider this example:

public class Container
{
    public Animal Animal { get; set; }
}

public class Animal
{
}

public class Dog : Animal
{
    public void Speak() { Console.WriteLine("Woof!"); }
}

var container = new Container { Animal = new Dog() };
var json = JsonSerializer.SerializeToString(container);
var container2 = JsonSerializer.DeserializeFromString<Container>(json);

((Dog)container.Animal).Speak(); //Works
((Dog)container2.Animal).Speak(); //InvalidCastException

最后一行抛出 InvalidCastException，因为 Animal 字段被实例化为 Animal 类型，而不是 Dog 类型.有什么方法可以告诉 ServiceStack 保留这个特定实例是 Dog 类型的信息吗?

The last line throws a InvalidCastException, because the Animal field is instantiated as an Animal type, not a Dog type. Is there any way I can tell ServiceStack to retain the information that this particular instance was of the Dog type?

推荐答案

在 DTO 中继承是一个坏主意 - DTO 应该尽可能地自我描述，并且通过使用继承，客户端实际上不知道服务最终返回什么.这就是为什么您的 DTO 类无法在大多数基于标准"的序列化程序中正确反序列化的原因.

Inheritance in DTOs is a bad idea - DTO's should be as self-describing as possible and by using inheritance clients effectively have no idea what the service ultimately returns. Which is why your DTO classes will fail to de/serialize properly in most 'standards-based' serializers.

没有充分的理由在 DTO 中使用接口(在 POCO 模型上使用它们的理由也很少)，使用接口来减少应用程序代码中的耦合是一种货物崇拜习惯，这些代码会被轻率地泄露到 DTO 中.但是跨进程边界，接口只会增加耦合(它只是在代码中减少)，因为消费者不知道要反序列化的具体类型，所以它必须发出特定于序列化的实现提示，现在将 C# 关注点嵌入到线路上(所以现在甚至C# 命名空间将中断序列化)，现在将您的响应限制为由特定的序列化程序使用.在线路上泄露 C# 问题违反了服务实现互操作性的核心目标之一.

There's no good reason for having interfaces in DTO's (and very few reasons to have them on POCO models), it's a cargo cult habit of using interfaces to reduce coupling in application code that's being thoughtlessly leaked into DTOs. But across process boundaries, interfaces only adds coupling (it's only reduced in code) since the consumer has no idea what concrete type to deserialize into so it has to emit serialization-specific implementation hints that now embeds C# concerns on the wire (so now even C# namespaces will break serialization) and now constrains your response to be used by a particular serializer. Leaking C# concerns on the wire violates one of the core goal of services for enabling interoperability.

由于 JSON 规范中没有类型信息"的概念，为了让继承在 JSON 序列化器中工作，它们需要向 /www.json.org/">JSON 线格式 包含此类型信息 - 现在将您的 JSON 有效负载耦合到特定的 JSON 序列化器实现.