StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POWhy does the XmlRoot attribute gets ignored in WCF and how to overcome this
primarykey
Id
2013689
data
AcceptedAnswerId
2076796
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-01-06T14:50:56.627
FavoriteCount
4
LastActivityDate
2012-11-28T10:55:24.553
LastEditDate
2017-05-23T12:22:05.467
LastEditorUserId
-1
OwnerUserId
43541
ParentId
0
PostTypeId
1
Score
8
ViewCount
5387
LastEditorDisplayName
text
Body
We've observed that when we expose a WCF service which uses classes decorated with various xml serialisation attributes, despite the fact that we use the XmlSerializerFormat attribute on the interface any XmlRoot attribute on any of the operation's parameters gets completely ignored. The namespace of the parameters is always that of the service and not what we specify. This is causing us problems as it does not seem to be backwards compatible with ASMX and also because we're using BizTalk, and need to have tighter control over the shape of the XML's exchanged. A few questions then - <ol> <li>Anybody knows what is the rationale behind this decision?</li> <li>Anybody knows how this is happening? I was under the impressions that WCF, with the XmlSerializerFormat attribute, uses the XmlSerialiser to serialise the types, which would suggest XmlRoot should be taken into account, how come this is not the case? (is it only due to the fact that, taking the SOAP envelope into account, the parameter is not root?)</li> <li>Most importantly - anybody knows if there's a way to 'force the issue' - i.e. get the parameters to be of the namespace of our choosing?</li> </ol> I've seen <a href="https://stackoverflow.com/questions/159373/xmlroot-attribute-not-included-in-the-generated-proxy-class">this</a> post, but I don't believe it is relevant to my question - As per Wagner Silveira's request - the contracts I used to test this are - <pre><code>[ServiceContract(Namespace = "http://servicecontract"), XmlSerializerFormat(Style = OperationFormatStyle.Document)] public interface ITestService { [OperationContract] MyOtherType MyTestMethod(MyType obj); } // Composite class for DCS and XMLS [Serializable, XmlType, XmlRoot(Namespace = "http://datacontract")] public class MyType { [XmlAttribute] public string StringValue { get; set; } } // Composite class for DCS and XMLS [Serializable, XmlType, XmlRoot(Namespace = "http://datacontract")] public class MyOtherType { [XmlAttribute] public string OtherStringValue { get; set; } } </code></pre>
Tags
<wcf><xml-serialization>
Title
Why does the XmlRoot attribute gets ignored in WCF and how to overcome this
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USYossi Dahan
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.