DOM CreateElement?

[Arpan]

Using DOM, this is how I am appending data to an existing XML file
which is named AppendData.xml (the root element of AppendData.xml is
<ProductList> ):

<script runat="server">
Sub Page_Load(ByVal obj As Object, ByVal ea As EventArgs)
Dim xmlDoc As New XmlDocument()
xmlDoc.Load(Ser ver.MapPath("Ap pendData.xml"))

Dim eltProducts1 As XmlElement = xmlDoc.CreateEl ement("Products ")
Dim attProdID1 As XmlAttribute = xmlDoc.CreateAt tribute("ProdID 1")

eltProducts1.Se tAttributeNode( attProdID1)
eltProducts1.Se tAttribute("Pro dID1", "PID1")

Dim eltRoot1 As XmlElement = xmlDoc.Item("Pr oductList")
eltRoot1.Append Child(eltProduc ts1)

Dim eltName1 As XmlElement = xmlDoc.CreateEl ement("Name")
eltName1.InnerT ext = "Product1"
eltProducts1.Ap pendChild(eltNa me1)

Dim eltDescription1 As XmlElement =
xmlDoc.CreateEl ement("Descript ion")
eltDescription1 .InnerText = "Desc1"
eltProducts1.Ap pendChild(eltDe scription1)

Dim eltUnitPrice1 As XmlElement = xmlDoc.CreateEl ement("UnitPric e")
eltUnitPrice1.I nnerText = "250"
eltProducts1.Ap pendChild(eltUn itPrice1)

Dim eltProducts2 As XmlElement = xmlDoc.CreateEl ement("Products ")
Dim attProdID2 As XmlAttribute = xmlDoc.CreateAt tribute("ProdID 2")

eltProducts2.Se tAttributeNode( attProdID2)
eltProducts2.Se tAttribute("Pro dID2", "PID2")

Dim eltRoot2 As XmlElement = xmlDoc.Item("Pr oductList")
eltRoot2.Append Child(eltProduc ts2)

Dim eltName2 As XmlElement = xmlDoc.CreateEl ement("Name")
eltName2.InnerT ext = "Product2"
eltProducts2.Ap pendChild(eltNa me2)

Dim eltDescription2 As XmlElement =
xmlDoc.CreateEl ement("Descript ion")
eltDescription2 .InnerText = "Desc2"
eltProducts2.Ap pendChild(eltDe scription2)

Dim eltUnitPrice2 As XmlElement = xmlDoc.CreateEl ement("UnitPric e")
eltUnitPrice2.I nnerText = "200"
eltProducts2.Ap pendChild(eltUn itPrice2)

xmlDoc.Save(Ser ver.MapPath("Ap pendData.xml"))
End Sub
</script>

The above code successfully appends 2 sets of <Productsdata to the
AppendData.xml file which looks like this:

<ProductList>
<Products ProdID="PID1">
<Name>Product 1</Name>
<Description>De sc1</Description>
<UnitPrice>25 0</UnitPrice>
</Products>
<Products ProdID="PID2">
<Name>Product 2</Name>
<Description>De sc2</Description>
<UnitPrice>20 0</UnitPrice>
</Products>
</ProductList>

Note that in order to append 2 sets of <Productsdata to
AppendData.xml, I have used 2 different variables to append the 2 sets
of <Productsdata i.e. for the attribute ProdID, I used attProdID1 &
attProdID2, for the element Name, I used eltName1 & eltName2, for the
element Description, I used eltDescription1 & eltDescription2 & finally
for UnitPrice, I used eltUnitPrice1 & eltUnitPrice2. Had I used only 1
variable (say, attProdID for the attribute ProdID, eltName for the
element Name, eltDescription for the element Description & eltUnitPrice
for the element UnitPrice) to append the 2 sets of <Productsdata ,
only the 2nd set of <Productsdata would get appended to
AppendData.xml.

What I did like to know is - to append more than 1 set of <Products>
data to AppendData.xml, is there some other way out wherein using a
single variable for the attribute ProdID & elements Name, Description &
UnitPrice would create multiple sets of <Productsdata (by using
loops, maybe) instead of using different variables for the attribute
ProdID & elements Name, Description & UnitPrice to append each set of
<Productsdata (as shown in the ASPX code above)?

Thanks,

Arpan

[Martin Honnen]

Arpan wrote:

The above code successfully appends 2 sets of <Productsdata to the
AppendData.xml file which looks like this:

<ProductList>
<Products ProdID="PID1">
<Name>Product 1</Name>
<Description>De sc1</Description>
<UnitPrice>25 0</UnitPrice>
</Products>
<Products ProdID="PID2">
<Name>Product 2</Name>
<Description>De sc2</Description>
<UnitPrice>20 0</UnitPrice>
</Products>
</ProductList>

Note that in order to append 2 sets of <Productsdata to
AppendData.xml, I have used 2 different variables to append the 2 sets
of <Productsdata i.e. for the attribute ProdID, I used attProdID1 &
attProdID2, for the element Name, I used eltName1 & eltName2, for the
element Description, I used eltDescription1 & eltDescription2 & finally
for UnitPrice, I used eltUnitPrice1 & eltUnitPrice2. Had I used only 1
variable (say, attProdID for the attribute ProdID, eltName for the
element Name, eltDescription for the element Description & eltUnitPrice
for the element UnitPrice) to append the 2 sets of <Productsdata ,
only the 2nd set of <Productsdata would get appended to
AppendData.xml.

I don't see any problem using one variable for each element type as long
as you create each element as needed and insert it e.g.

Dim Products As XmlElement
Dim Name As XmlElement
Dim Description As XmlElement
Dim UnitPrice As XmlElement

Products = xmlDoc.CreateEl ement("Products ")
Products.SetAtt ribute("ProdID" , "PID1")

Name = xmlDoc.CreateEl ement("Name")
Name.InnerText = "Product1"

Products.Append Child(Name)

Description = xmlDoc.CreateEl ement("Descript ion")
Description.Inn erText = "Desc1"

Products.Append Child(Descripti on)

UnitPrice = xmlDoc.CreateEl ement("UnitPric e")
UnitPrice.Inner Text = "250"

Products.Append Child(UnitPrice )

xmlDoc.Document Element.AppendC hild(Products)

Products = xmlDoc.CreateEl ement("Products ")
Products.SetAtt ribute("ProdID" , "PID2")

Name = xmlDoc.CreateEl ement("Name")
Name.InnerText = "Product2"

Products.Append Child(Name)

Description = xmlDoc.CreateEl ement("Descript ion")
Description.Inn erText = "Desc2"

Products.Append Child(Descripti on)

UnitPrice = xmlDoc.CreateEl ement("UnitPric e")
UnitPrice.Inner Text = "200"

Products.Append Child(UnitPrice )

xmlDoc.Document Element.AppendC hild(Products)

xmlDoc.Save(Ser ver.MapPath("fi le.xml"))

There is also no need to create attribute nodes if you simply use the
SetAttribute method on an XmlElement node anyway.

--

Martin Honnen --- MVP XML
http://JavaScript.FAQTs.com/

[Arpan]

Thanks Martin, your suggestions have really been very very helpful.
After going through your code, I realized that retrieving the root
element <ProductListusi ng

Dim eltRoot1 As XmlElement = xmlDoc.Item("Pr oductList"))

(as shown in the code in post #1) isn't necessary as well.

One last question please - what's the difference between a Node & an
Element in XML? Or are they one & the same?

Thanks once again,

Regards,

Arpan

Martin Honnen wrote:

Arpan wrote:

The above code successfully appends 2 sets of <Productsdata to the
AppendData.xml file which looks like this:

<ProductList>
<Products ProdID="PID1">
<Name>Product 1</Name>
<Description>De sc1</Description>
<UnitPrice>25 0</UnitPrice>
</Products>
<Products ProdID="PID2">
<Name>Product 2</Name>
<Description>De sc2</Description>
<UnitPrice>20 0</UnitPrice>
</Products>
</ProductList>

Note that in order to append 2 sets of <Productsdata to
AppendData.xml, I have used 2 different variables to append the 2 sets
of <Productsdata i.e. for the attribute ProdID, I used attProdID1 &
attProdID2, for the element Name, I used eltName1 & eltName2, for the
element Description, I used eltDescription1 & eltDescription2 & finally
for UnitPrice, I used eltUnitPrice1 & eltUnitPrice2. Had I used only 1
variable (say, attProdID for the attribute ProdID, eltName for the
element Name, eltDescription for the element Description & eltUnitPrice
for the element UnitPrice) to append the 2 sets of <Productsdata ,
only the 2nd set of <Productsdata would get appended to
AppendData.xml.

I don't see any problem using one variable for each element type as long
as you create each element as needed and insert it e.g.

Dim Products As XmlElement
Dim Name As XmlElement
Dim Description As XmlElement
Dim UnitPrice As XmlElement

Products = xmlDoc.CreateEl ement("Products ")
Products.SetAtt ribute("ProdID" , "PID1")

Name = xmlDoc.CreateEl ement("Name")
Name.InnerText = "Product1"

Products.Append Child(Name)

Description = xmlDoc.CreateEl ement("Descript ion")
Description.Inn erText = "Desc1"

Products.Append Child(Descripti on)

UnitPrice = xmlDoc.CreateEl ement("UnitPric e")
UnitPrice.Inner Text = "250"

Products.Append Child(UnitPrice )

xmlDoc.Document Element.AppendC hild(Products)

Products = xmlDoc.CreateEl ement("Products ")
Products.SetAtt ribute("ProdID" , "PID2")

Name = xmlDoc.CreateEl ement("Name")
Name.InnerText = "Product2"

Products.Append Child(Name)

Description = xmlDoc.CreateEl ement("Descript ion")
Description.Inn erText = "Desc2"

Products.Append Child(Descripti on)

UnitPrice = xmlDoc.CreateEl ement("UnitPric e")
UnitPrice.Inner Text = "200"

Products.Append Child(UnitPrice )

xmlDoc.Document Element.AppendC hild(Products)

xmlDoc.Save(Ser ver.MapPath("fi le.xml"))

There is also no need to create attribute nodes if you simply use the
SetAttribute method on an XmlElement node anyway.

--

Martin Honnen --- MVP XML
http://JavaScript.FAQTs.com/

[Martin Honnen]

Arpan wrote:

One last question please - what's the difference between a Node & an
Element in XML? Or are they one & the same?

There are many different views and models and specifications. The XML
specification itself <http://www.w3.org/TR/REC-xml/does not talk about
nodes at all but object models do.
In the DOM data model and in the XPath data model there is a base type,
the node, and there are specializations of the node type.
So any element in the DOM is a node, an element node, but there are
other types of nodes, for instance text nodes, attribute nodes,
processing instruction nodes, comment nodes, the document node.
In the .NET DOM object model/class hierarchy that is reflected, there is
an abstract base class XmlNode from which several other node types are
derived
<http://msdn.microsoft. com/library/default.asp?url =/library/en-us/cpref/html/frlrfsystemxmlx mlnodeclasshier archy.asp>
<http://msdn.microsoft. com/library/default.asp?url =/library/en-us/cpref/html/frlrfsystemxmlx mllinkednodecla sshierarchy.asp >

As said, the XPath data model also knows nodes in general and
specializations of that general node type, like element nodes, attribute
nodes, text nodes, comment nodes, processing instruction nodes. There
are however some differences between how XPath models certain things in
an XML document and how the DOM models the same things. For instance XML
namespace declarations you find in XML document with namespace e.g.
<element xmlns="http://example.com/ns1">
or
<element xmlns:xlink="ht tp://www.w3.org/1999/xlink"
xlink:href="htt p://example.org/2006/ex1">
are simply modelled as attribute nodes in the DOM while the XPath data
model does not have those namespace declarations as attributes but
rather introduces special namespace nodes.
--

Martin Honnen --- MVP XML
http://JavaScript.FAQTs.com/