|
|
You're in the
dotnet xml
group:XmlDocument and DataBinding
dotnet xml:
Allen Evans posted the XmlNodeList approach a while ago [0] as the way to bind data to ASP.NET controls -- and Kirk would know ;) Alternatively, you could read the XML into a DataSet if your format permits. HTH, Christoph Schittko MS MVP XML http://weblogs.asp.net/cschittko [0] http://blogs.msdn.com/kaevans/archive/2003/07/04/9713.aspx [quoted text, click to view] > -----Original Message----- > From: pete [mailto:no_spam@hotmail.com] > Posted At: Friday, November 26, 2004 11:59 AM > Posted To: microsoft.public.dotnet.xml > Conversation: XmlDocument and DataBinding > Subject: XmlDocument and DataBinding > > Hi there, > > Can someone explain to me why I can't bind to an XmlDocument but I can > bind > to an XmlNodeList. It's my understanding that they both implement the > IEnumerable interface which is required for databinding. Am happy to work > with the XmlNodeList but I can't shake the feeling I'm missing something > <blush> > > Thanks, Pete
Hi there,
Can someone explain to me why I can't bind to an XmlDocument but I can bind to an XmlNodeList. It's my understanding that they both implement the IEnumerable interface which is required for databinding. Am happy to work with the XmlNodeList but I can't shake the feeling I'm missing something <blush> Thanks, Pete
It's my understanding that XmlDocument inherits its implementation of
IEnumerable interface from the XmlNode type. Here is the doc: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemxmlxmlnodeclasstopic.asp. However, by looking at the documentation for the IEnumerable interface its clear that XmlDocument isn't one of the classes that supports it. I guess the question I'm asking is, if XmlNode is IEnumerable then why isn't XmlDocument? Cheers, Pete [quoted text, click to view] "Martin Honnen" <mahotrash@yahoo.de> wrote in message news:%23MCwSj%230EHA.3448@TK2MSFTNGP09.phx.gbl... > > > pete wrote: > > > > Can someone explain to me why I can't bind to an XmlDocument but I can bind > > to an XmlNodeList. It's my understanding that they both implement the > > IEnumerable interface which is required for databinding. Am happy to work > > with the XmlNodeList but I can't shake the feeling I'm missing something > > Here are the docs: > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemXmlXmlNodeListClassTopic.asp > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemXmlXmlDocumentClassTopic.asp > there is nothing there indicating that XmlDocument implements the > IEnumerable interface so you can bind to it. > > > > > -- > > Martin Honnen > http://JavaScript.FAQTs.com/
[quoted text, click to view] pete wrote: [quoted text, click to view] > Can someone explain to me why I can't bind to an XmlDocument but I can bind > to an XmlNodeList. It's my understanding that they both implement the > IEnumerable interface which is required for databinding. Am happy to work > with the XmlNodeList but I can't shake the feeling I'm missing something Here are the docs: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemXmlXmlNodeListClassTopic.asp http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemXmlXmlDocumentClassTopic.asp there is nothing there indicating that XmlDocument implements the IEnumerable interface so you can bind to it. -- Martin Honnen
[quoted text, click to view] pete wrote: > It's my understanding that XmlDocument inherits its implementation of > IEnumerable interface from the XmlNode type. Here is the doc: > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemxmlxmlnodeclasstopic.asp. > However, by looking at the documentation for the IEnumerable interface its > clear that XmlDocument isn't one of the classes that supports it. > > I guess the question I'm asking is, if XmlNode is IEnumerable then why isn't > XmlDocument? You are right, as XmlNode implements IEnumerable XmlDocument inherits that implementation. And thus XmlDocument can be bound as in the following example: <%@ Page Language="C#" %> <%@ Import Namespace="System.Xml" %> <html> <head> <title>binding an XmlDocument to a DataList</title> <script runat="server"> void Page_Load () { XmlDocument xmlDocument = new XmlDocument(); xmlDocument.PreserveWhitespace = true; xmlDocument.LoadXml(@"<?xml version=""1.0""?> <!-- Kibology for all --> <gods> <god>Kibo</god> <god>Xibo</god> </gods>"); DataList1.DataSource = xmlDocument; DataList1.DataBind(); } </script> </head> <body> <form runat="server"> <asp:DataList id="DataList1" runat="server"> <ItemTemplate> <%#((System.Xml.XmlNode)Container.DataItem).NodeType%> </ItemTemplate> </asp:DataList> </form> </body> </html> which then outputs XmlDeclaration Whitespace Comment Whitespace Element So what the enumerator for an XmlDocument does is enumerating the top level child nodes and you can bind those if you are interested in them. Only the data in an XML document is usually not contained directly in top level child nodes of the document itself but in child nodes and descendants of the document element and if you want to display that data you need to first access the child nodes or descendants so that is why you will probably end up using a node list returned by SelectNodes or GetElementsByTagName. -- Martin Honnen
Thanks for the explanation martin. I didn't expect to be able to use the
IEnumerable interface of the XmlDocument in any sensible way but was curious why I couldn't use it at all. In your example, I notice that you use explicit casting in your databinding expression rather than DataBinder.Eval(). Is there any reason for this? Cheers, Pete [quoted text, click to view] "Martin Honnen" <mahotrash@yahoo.de> wrote in message news:ukiBpXJ1EHA.2600@TK2MSFTNGP09.phx.gbl... > > > pete wrote: > > > It's my understanding that XmlDocument inherits its implementation of > > IEnumerable interface from the XmlNode type. Here is the doc: > > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfsystemxmlxmlnodeclasstopic.asp. > > However, by looking at the documentation for the IEnumerable interface its > > clear that XmlDocument isn't one of the classes that supports it. > > > > I guess the question I'm asking is, if XmlNode is IEnumerable then why isn't > > XmlDocument? > > You are right, as XmlNode implements IEnumerable XmlDocument inherits > that implementation. And thus XmlDocument can be bound as in the > following example: > > <%@ Page Language="C#" %> > <%@ Import Namespace="System.Xml" %> > <html> > <head> > <title>binding an XmlDocument to a DataList</title> > <script runat="server"> > void Page_Load () { > XmlDocument xmlDocument = new XmlDocument(); > xmlDocument.PreserveWhitespace = true; > xmlDocument.LoadXml(@"<?xml version=""1.0""?> > <!-- Kibology for all --> > <gods> > <god>Kibo</god> > <god>Xibo</god> > </gods>"); > DataList1.DataSource = xmlDocument; > DataList1.DataBind(); > } > </script> > </head> > <body> > <form runat="server"> > <asp:DataList id="DataList1" runat="server"> > <ItemTemplate> > <%#((System.Xml.XmlNode)Container.DataItem).NodeType%> > </ItemTemplate> > </asp:DataList> > </form> > </body> > </html> > > which then outputs > > XmlDeclaration > Whitespace > Comment > Whitespace > Element > > So what the enumerator for an XmlDocument does is enumerating the top > level child nodes and you can bind those if you are interested in them. > Only the data in an XML document is usually not contained directly in > top level child nodes of the document itself but in child nodes and > descendants of the document element and if you want to display that data > you need to first access the child nodes or descendants so that is why > you will probably end up using a node list returned by SelectNodes or > GetElementsByTagName. > > -- > > Martin Honnen > http://JavaScript.FAQTs.com/
Pete,
It might also be interesting to you that Visual Studio 2005 ships with an XmlDataSource object to bind XML data to web server controls [0]. Note that Microsoft did not make the XmlDocument itself bindable but followed the general provider pattern in ASP.NET 2.0 to enable binding of XML data. HTH, Christoph Schittko MVP XML http://weblogs.asp.net/cschittko [0] http://msdn2.microsoft.com/library/e8d8587a.aspx [quoted text, click to view] > -----Original Message----- > From: pete [mailto:no_spam@hotmail.com] > Posted At: Saturday, November 27, 2004 7:16 PM > Posted To: microsoft.public.dotnet.xml > Conversation: XmlDocument and DataBinding > Subject: Re: XmlDocument and DataBinding > > Thanks for the explanation martin. I didn't expect to be able to use the > IEnumerable interface of the XmlDocument in any sensible way but was > curious > why I couldn't use it at all. In your example, I notice that you use > explicit casting in your databinding expression rather than > DataBinder.Eval(). Is there any reason for this? > > Cheers, Pete > > "Martin Honnen" <mahotrash@yahoo.de> wrote in message > news:ukiBpXJ1EHA.2600@TK2MSFTNGP09.phx.gbl... > > > > > > pete wrote: > > > > > It's my understanding that XmlDocument inherits its implementation of > > > IEnumerable interface from the XmlNode type. Here is the doc: > > > > http://msdn.microsoft.com/library/default.asp?url=/library/en- > us/cpref/html/frlrfsystemxmlxmlnodeclasstopic.asp. > > > However, by looking at the documentation for the IEnumerable interface > its > > > clear that XmlDocument isn't one of the classes that supports it. > > > > > > I guess the question I'm asking is, if XmlNode is IEnumerable then why > isn't > > > XmlDocument? > > > > You are right, as XmlNode implements IEnumerable XmlDocument inherits > > that implementation. And thus XmlDocument can be bound as in the > > following example: > > > > <%@ Page Language="C#" %> > > <%@ Import Namespace="System.Xml" %> > > <html> > > <head> > > <title>binding an XmlDocument to a DataList</title> > > <script runat="server"> > > void Page_Load () { > > XmlDocument xmlDocument = new XmlDocument(); > > xmlDocument.PreserveWhitespace = true; > > xmlDocument.LoadXml(@"<?xml version=""1.0""?> > > <!-- Kibology for all --> > > <gods> > > <god>Kibo</god> > > <god>Xibo</god> > > </gods>"); > > DataList1.DataSource = xmlDocument; > > DataList1.DataBind(); > > } > > </script> > > </head> > > <body> > > <form runat="server"> > > <asp:DataList id="DataList1" runat="server"> > > <ItemTemplate> > > <%#((System.Xml.XmlNode)Container.DataItem).NodeType%> > > </ItemTemplate> > > </asp:DataList> > > </form> > > </body> > > </html> > > > > which then outputs > > > > XmlDeclaration > > Whitespace > > Comment > > Whitespace > > Element > > > > So what the enumerator for an XmlDocument does is enumerating the top > > level child nodes and you can bind those if you are interested in them. > > Only the data in an XML document is usually not contained directly in > > top level child nodes of the document itself but in child nodes and > > descendants of the document element and if you want to display that data > > you need to first access the child nodes or descendants so that is why > > you will probably end up using a node list returned by SelectNodes or > > GetElementsByTagName. > > > > -- > > > > Martin Honnen > > http://JavaScript.FAQTs.com/
[quoted text, click to view] pete wrote: [quoted text, click to view] > In your example, I notice that you use > explicit casting in your databinding expression rather than > DataBinder.Eval(). Is there any reason for this? No, no particular reason, certainly none related to XmlDocument, I was just adapting an example using that syntax. -- Martin Honnen
Pete,
Thats certainly sounds a whole lot more flexible. I'll get chance to play around with the beta one day ... happy grin ... one day Peter [quoted text, click to view] "Christoph Schittko [MVP]" <INVALIDEMAIL@austin.rr.com> wrote in message news:%23wAaZeW1EHA.1308@TK2MSFTNGP09.phx.gbl... > Pete, > > It might also be interesting to you that Visual Studio 2005 ships with > an XmlDataSource object to bind XML data to web server controls [0]. > Note that Microsoft did not make the XmlDocument itself bindable but > followed the general provider pattern in ASP.NET 2.0 to enable binding > of XML data. > > HTH, > Christoph Schittko > MVP XML > http://weblogs.asp.net/cschittko > > [0] http://msdn2.microsoft.com/library/e8d8587a.aspx > > > -----Original Message----- > > From: pete [mailto:no_spam@hotmail.com] > > Posted At: Saturday, November 27, 2004 7:16 PM > > Posted To: microsoft.public.dotnet.xml > > Conversation: XmlDocument and DataBinding > > Subject: Re: XmlDocument and DataBinding > > > > Thanks for the explanation martin. I didn't expect to be able to use > the > > IEnumerable interface of the XmlDocument in any sensible way but was > > curious > > why I couldn't use it at all. In your example, I notice that you use > > explicit casting in your databinding expression rather than > > DataBinder.Eval(). Is there any reason for this? > > > > Cheers, Pete > > > > "Martin Honnen" <mahotrash@yahoo.de> wrote in message > > news:ukiBpXJ1EHA.2600@TK2MSFTNGP09.phx.gbl... > > > > > > > > > pete wrote: > > > > > > > It's my understanding that XmlDocument inherits its implementation > of > > > > IEnumerable interface from the XmlNode type. Here is the doc: > > > > > > http://msdn.microsoft.com/library/default.asp?url=/library/en- > > us/cpref/html/frlrfsystemxmlxmlnodeclasstopic.asp. > > > > However, by looking at the documentation for the IEnumerable > interface > > its > > > > clear that XmlDocument isn't one of the classes that supports it. > > > > > > > > I guess the question I'm asking is, if XmlNode is IEnumerable then > why > > isn't > > > > XmlDocument? > > > > > > You are right, as XmlNode implements IEnumerable XmlDocument > inherits > > > that implementation. And thus XmlDocument can be bound as in the > > > following example: > > > > > > <%@ Page Language="C#" %> > > > <%@ Import Namespace="System.Xml" %> > > > <html> > > > <head> > > > <title>binding an XmlDocument to a DataList</title> > > > <script runat="server"> > > > void Page_Load () { > > > XmlDocument xmlDocument = new XmlDocument(); > > > xmlDocument.PreserveWhitespace = true; > > > xmlDocument.LoadXml(@"<?xml version=""1.0""?> > > > <!-- Kibology for all --> > > > <gods> > > > <god>Kibo</god> > > > <god>Xibo</god> > > > </gods>"); > > > DataList1.DataSource = xmlDocument; > > > DataList1.DataBind(); > > > } > > > </script> > > > </head> > > > <body> > > > <form runat="server"> > > > <asp:DataList id="DataList1" runat="server"> > > > <ItemTemplate> > > > <%#((System.Xml.XmlNode)Container.DataItem).NodeType%> > > > </ItemTemplate> > > > </asp:DataList> > > > </form> > > > </body> > > > </html> > > > > > > which then outputs > > > > > > XmlDeclaration > > > Whitespace > > > Comment > > > Whitespace > > > Element > > > > > > So what the enumerator for an XmlDocument does is enumerating the > top > > > level child nodes and you can bind those if you are interested in > them. > > > Only the data in an XML document is usually not contained directly > in > > > top level child nodes of the document itself but in child nodes and > > > descendants of the document element and if you want to display that > data > > > you need to first access the child nodes or descendants so that is > why > > > you will probably end up using a node list returned by SelectNodes > or > > > GetElementsByTagName. > > > > > > -- > > > > > > Martin Honnen > > > http://JavaScript.FAQTs.com/ > >
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 |