| Groups | Blog | Home |
dotnet xml : Avoiding XML serialization namespace substitution?
I have a class that I wish to serialize to XML, part of which looks like this: public class TitleNotification { [XmlAttributeAttribute(Namespace="xsi", AttributeName="noNameSpaceSchemaLocation")] public string NoNameSpaceSchemaLocation = http://www.pdr.com\nhttps://extw3c.pdr.com/prism/b2b/schemas/TitleNotification.xsd; .... } When the class is serialized, the relevant resulting XML looks like this: <?xml version="1.0" encoding="utf-8"?> <TitleNotification xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" d1p1:noNameSpaceSchemaLocation="http://www.pdr.com
https://extw3c.pdr.co m/prism/b2b/schemas/TitleNotification.xsd" ParagonID="1234" Version="1" Source="5" SupplierID="PA-1234" xmlns:d1p1="xsi" ... How can I get it to generate xsi:noNameSpaceSchemaLocation instead of doing the d1p1 substitution thing it's doing now? Thanks, Adam
[quoted text, click to view]
"AP" <adamp@indra.com> wrote in message news:OAU8iiJLEHA.3808@TK2MSFTNGP12.phx.gbl... > I have a class that I wish to serialize to XML, part of which looks like > this: > > public class TitleNotification { > [XmlAttributeAttribute(Namespace="xsi", > AttributeName="noNameSpaceSchemaLocation")] The Namespace property represents a namespace URI -- not a prefix. [XmlAttribute( Namespace="http://www.w3.org/2001/XMLSchema-instance", AttributeName="noNamespaceSchemaLocation")] Also observe that the QName, xsi:noNamespaceSchemaLocation, is case-sensitive. : : [quoted text, click to view] > How can I get it to generate xsi:noNameSpaceSchemaLocation instead of doing > the d1p1 substitution thing it's doing now? Try using the namespace URI, XmlSerializer may re-use the xsi prefix. If it doesn't, then it's choice of prefix is arbitrary. Correct implementations that honor xsi:noNamespaceSchemaLocation are actually looking for: {http://www.w3.org/2001/XMLSchema-instance,noNamespaceSchemaLocation} Therefore, it doesn't matter what prefix it's given. Ordinarily, you would use a public field of type XmlSerializerNamespaces, and mark it with the [XmlNamespaceDeclarations] attribute. You could initialize this field by Add'ing prefix and namespaceURI pairings into it. However, the XML Schema namespace declarations are emitted by the XmlSerializer prior to consulting the XmlNamespaceDeclarations field, so you cannot count on your xsi namespace declaration appearing early enough in the root element (it'll be there, though, because XmlSerializer needs the XMLSchema-instance namespace itself.) Derek Harmon
So in other words there's no gauranteed way of doing it?
[quoted text, click to view] "Derek Harmon" <loresayer@msn.com> wrote in message news:eQT4yeLLEHA.268@TK2MSFTNGP11.phx.gbl... > "AP" <adamp@indra.com> wrote in message news:OAU8iiJLEHA.3808@TK2MSFTNGP12.phx.gbl... > > I have a class that I wish to serialize to XML, part of which looks like > > this: > > > > public class TitleNotification { > > [XmlAttributeAttribute(Namespace="xsi", > > AttributeName="noNameSpaceSchemaLocation")] > > The Namespace property represents a namespace URI -- not a prefix. > > [XmlAttribute( Namespace="http://www.w3.org/2001/XMLSchema-instance", > AttributeName="noNamespaceSchemaLocation")] > > Also observe that the QName, xsi:noNamespaceSchemaLocation, is > case-sensitive. > > : : > > How can I get it to generate xsi:noNameSpaceSchemaLocation instead of doing > > the d1p1 substitution thing it's doing now? > > Try using the namespace URI, XmlSerializer may re-use the xsi prefix. > If it doesn't, then it's choice of prefix is arbitrary. Correct implementations > that honor xsi:noNamespaceSchemaLocation are actually looking for: > > {http://www.w3.org/2001/XMLSchema-instance,noNamespaceSchemaLocation} > > Therefore, it doesn't matter what prefix it's given. > > Ordinarily, you would use a public field of type XmlSerializerNamespaces, > and mark it with the [XmlNamespaceDeclarations] attribute. You could > initialize this field by Add'ing prefix and namespaceURI pairings into it. > > However, the XML Schema namespace declarations are emitted by the > XmlSerializer prior to consulting the XmlNamespaceDeclarations field, > so you cannot count on your xsi namespace declaration appearing early > enough in the root element (it'll be there, though, because XmlSerializer > needs the XMLSchema-instance namespace itself.) > > > Derek Harmon > >
You can get rid of the xsd and xsi namespace declarations by using the
technique explained here: http://weblogs.asp.net/cazzu/archive/2004/01/23/62141.aspx, at the very beginning of the post. HTH -- Daniel Cazzulino [MVP XML] Clarius Consulting SA http://weblogs.asp.net/cazzu http://aspnet2.com [quoted text, click to view] "Derek Harmon" <loresayer@msn.com> wrote in message news:eQT4yeLLEHA.268@TK2MSFTNGP11.phx.gbl... > "AP" <adamp@indra.com> wrote in message news:OAU8iiJLEHA.3808@TK2MSFTNGP12.phx.gbl... > > I have a class that I wish to serialize to XML, part of which looks like > > this: > > > > public class TitleNotification { > > [XmlAttributeAttribute(Namespace="xsi", > > AttributeName="noNameSpaceSchemaLocation")] > > The Namespace property represents a namespace URI -- not a prefix. > > [XmlAttribute( Namespace="http://www.w3.org/2001/XMLSchema-instance", > AttributeName="noNamespaceSchemaLocation")] > > Also observe that the QName, xsi:noNamespaceSchemaLocation, is > case-sensitive. > > : : > > How can I get it to generate xsi:noNameSpaceSchemaLocation instead of doing > > the d1p1 substitution thing it's doing now? > > Try using the namespace URI, XmlSerializer may re-use the xsi prefix. > If it doesn't, then it's choice of prefix is arbitrary. Correct implementations > that honor xsi:noNamespaceSchemaLocation are actually looking for: > > {http://www.w3.org/2001/XMLSchema-instance,noNamespaceSchemaLocation} > > Therefore, it doesn't matter what prefix it's given. > > Ordinarily, you would use a public field of type XmlSerializerNamespaces, > and mark it with the [XmlNamespaceDeclarations] attribute. You could > initialize this field by Add'ing prefix and namespaceURI pairings into it. > > However, the XML Schema namespace declarations are emitted by the > XmlSerializer prior to consulting the XmlNamespaceDeclarations field, > so you cannot count on your xsi namespace declaration appearing early > enough in the root element (it'll be there, though, because XmlSerializer > needs the XMLSchema-instance namespace itself.) > > > Derek Harmon > > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.665 / Virus Database: 428 - Release Date: 23/04/2004
Well, not quite what you wanted anyway :S
-- Daniel Cazzulino [MVP XML] Clarius Consulting SA http://weblogs.asp.net/cazzu http://aspnet2.com [quoted text, click to view] "Daniel Cazzulino [MVP XML]" <kzuAT@NOaspnet2SPAMPLZ.com> wrote in message news:#3Im7LXLEHA.3324@TK2MSFTNGP10.phx.gbl... > You can get rid of the xsd and xsi namespace declarations by using the > technique explained here: > http://weblogs.asp.net/cazzu/archive/2004/01/23/62141.aspx, at the very > beginning of the post. > > HTH > -- > Daniel Cazzulino [MVP XML] > Clarius Consulting SA > http://weblogs.asp.net/cazzu > http://aspnet2.com > "Derek Harmon" <loresayer@msn.com> wrote in message > news:eQT4yeLLEHA.268@TK2MSFTNGP11.phx.gbl... > > "AP" <adamp@indra.com> wrote in message > news:OAU8iiJLEHA.3808@TK2MSFTNGP12.phx.gbl... > > > I have a class that I wish to serialize to XML, part of which looks like > > > this: > > > > > > public class TitleNotification { > > > [XmlAttributeAttribute(Namespace="xsi", > > > AttributeName="noNameSpaceSchemaLocation")] > > > > The Namespace property represents a namespace URI -- not a prefix. > > > > [XmlAttribute( Namespace="http://www.w3.org/2001/XMLSchema-instance", > > AttributeName="noNamespaceSchemaLocation")] > > > > Also observe that the QName, xsi:noNamespaceSchemaLocation, is > > case-sensitive. > > > > : : > > > How can I get it to generate xsi:noNameSpaceSchemaLocation instead of > doing > > > the d1p1 substitution thing it's doing now? > > > > Try using the namespace URI, XmlSerializer may re-use the xsi prefix. > > If it doesn't, then it's choice of prefix is arbitrary. Correct > implementations > > that honor xsi:noNamespaceSchemaLocation are actually looking for: > > > > {http://www.w3.org/2001/XMLSchema-instance,noNamespaceSchemaLocation} > > > > Therefore, it doesn't matter what prefix it's given. > > > > Ordinarily, you would use a public field of type XmlSerializerNamespaces, > > and mark it with the [XmlNamespaceDeclarations] attribute. You could > > initialize this field by Add'ing prefix and namespaceURI pairings into it. > > > > However, the XML Schema namespace declarations are emitted by the > > XmlSerializer prior to consulting the XmlNamespaceDeclarations field, > > so you cannot count on your xsi namespace declaration appearing early > > enough in the root element (it'll be there, though, because XmlSerializer > > needs the XMLSchema-instance namespace itself.) > > > > > > Derek Harmon > > > > > > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.665 / Virus Database: 428 - Release Date: 23/04/2004 > > --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.665 / Virus Database: 428 - Release Date: 23/04/2004
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |