All geek questions in one place

Unexpected behavior with requested XML node order item on ServiceStack WS

Now, since I know that ServiceStack uses the .NET Xml DataContractSerializer to serialize / deserialize XML, but with it we have some truble when our webservice API uses a non-.NET framework.

This problem is very well described in this post , if you try to briefly describe the problem:

Requiring a strict sequence of XML nodes is very inconvenient for some external no. NET

Is it possible to use another serializer or to configure the used ServiceStack so that it does not expect elements in hard-coded positions?

+1
source share
1 answer

ServiceStack uses the .NET XML DataContract serializer under the hood. It is not configurable beyond what is offered by the underlying .NET Framework.

I answered how to override the standard default XML serialization of ServiceStack using a custom XML serializer in this earlier question:

fooobar.com/questions/1497032 / ...

+1
source

Source: https://habr.com/ru/post/1497027/

More articles:


All Articles