<back to all web services
HelloWithEnumList
HelloWithEnumList Parameters:Name | Parameter | Data Type | Required | Description |
---|
EnumProp | query | List<EnumType> | Yes | |
EnumWithValues | query | List<EnumWithValues> | Yes | |
NullableEnumProp | query | List<Nullable<EnumType>> | Yes | |
EnumFlags | query | List<EnumFlags> | Yes | |
EnumStyle | query | List<EnumStyle> | Yes | |
EnumType Enum:Value1 | |
Value2 | |
Value3 | |
EnumWithValues Enum:Name | Value | |
---|
None | None | |
Value1 | Member 1 | |
Value2 | Value2 | Member 2 |
EnumFlags Enum:Name | Value | |
---|
Value0 | 0 | |
Value1 | 1 | |
Value2 | 2 | |
Value3 | 4 | |
Value123 | 7 | |
EnumStyle Enum:lower | |
UPPER | |
PascalCase | |
camelCase | |
camelUPPER | |
PascalUPPER | |
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
HTTP + XML
The following are sample HTTP requests and responses.
The placeholders shown need to be replaced with actual values.
POST /xml/oneway/HelloWithEnumList HTTP/1.1
Host: test.servicestack.net
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<HelloWithEnumList xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Test.ServiceModel">
<EnumFlags>
<EnumFlags>Value0</EnumFlags>
</EnumFlags>
<EnumProp>
<EnumType>Value1</EnumType>
</EnumProp>
<EnumStyle>
<EnumStyle>lower</EnumStyle>
</EnumStyle>
<EnumWithValues>
<EnumWithValues>None</EnumWithValues>
</EnumWithValues>
<NullableEnumProp xmlns:d2p1="http://schemas.datacontract.org/2004/07/System">
<d2p1:EnumType>Value1</d2p1:EnumType>
</NullableEnumProp>
</HelloWithEnumList>