XML / XSL

Choice of Value Types in Field

11-Sep-07 14:17

Either format is okay! However, the format without breaks loads and parses faster, saves disk space, and possibly some memory. By the way, if you want to make your XML file even smaller, use attributes wherever possible.

"We make a living by what we get, we make a life by what we give." --Winston Churchill

Brady Kelly11-Sep-07 1:38

Brady Kelly

11-Sep-07 1:38

I'm working on an XML schema for defining flat file layouts. I will be converting our current, template based[1] defintions to XML definitions, and was wondering about how best to express the options for the content of a column in a flat file, especially for exports, i.e. producing the file.

I'm looking at a sequence of Column[2] elements, where each Column element has a name, and a value source. Currently, the value sources are only ADO.NET columns in a data source, or literals. I would however like to expand the potential value sources to include functions etc.

My main concern is how to express the choice of value source. I'll use {} instead of angle brackets to show what I mean. My Column element would look something like:

{Column name="CustomerID" type="System.Int32"}
{DataField query="Customers" field="CustomerNo" /}
{Lookup table="xxx" ..... /}
{Literal}999{/Literal}
{/Column}

I could just use a literal value as a text node below the Column element, but that breaks consistency with the other content types. What suggestions can I get for expressing this?

[1] It is currently a very hard to maintain system where a record layout is defined as s string, with tabs, commas, etc. between output columns. If a non-delimiter string is surrounded by '%' characters, it is the name of a field from the data source to render into that column.

I do not believe they are right who say that the defects of famous men should be ignored. I think it is better that we should know them. Then, though we are conscious of having faults as glaring as theirs, we can believe that that is no hindrance to our achieving also something of their virtues. - W. Somerset Maugham

My New Blog

how to use the distinct-nodes function?

Rocky#11-Sep-07 0:30

generalizing the tabular display of xml data

11-Sep-07 0:30

Hi,
well I'm trying to use the distinct-nodes function and I've added all sorts of namespaces now. it looks like this:-

<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:fn="http://www.w3.org/2004/07/xpath-functions"
xmlns:functx="http://www.functx.com"
xmlns:msxsl="urn:schemas-microsoft-com:xslt"
xmlns:user="urn:my-scripts"
>
-------------------------------------------------
and I'm trying to use it like this:
<xsl:for-each select="functx:distinct-nodes('Inputs/*')">
<td><xsl:value-of select="name()"></xsl:value-of></td>
</xsl:for-each>
----------------------------------------------------
the error is this

The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.

--------------------------------------------------------------------------------

Namespace 'http://www.functx.com' does not contain any functions.

Can u plz help me with this, I can't seem to figure out where I'm going wrong

Thanks in advance

Rocky

You can't climb up a ladder with your hands in your pockets.

Rocky#10-Sep-07 20:23

How to XSL parse 300 mg XML file?

10-Sep-07 20:23

Hello everyone,
I'm back again with another problem!!

well I'm trying to display data from an Xml file in the form of a table. for that I'm using XSL and the problem is that now I wanna make the xsl able to display different number of columns in the table.
the data can be in any form such as
<Outputs>
<Compound>BiPhenyl</Compound>
<Value>0.000000005</Value>
<Compound>BiPhenyl</Compound>
<Value>0.000000005</Value>
<Compound>BiPhenyl</Compound>
<Value>0.000000005</Value>
<Compound>BiPhenyl</Compound>
<Value>0.000000005</Value>
<Compound>BiPhenyl</Compound>
<Value>0.000000005</Value>
<Compound>H2O</Compound>
<Value>0.703552320</Value>
</Outputs>

or...
<Outputs>
<Value>0.000018075</Value>
</Outputs>

and the headiings of the columns shoulbe the heading nodes. as you can see in teh previous example that the node name 'compound' and 'value' are reapeated every time for each value but i just need them once.

So the point is that there can be different number of columns to display. How can I make such an arrangement that the xsl should pick up the unique names of the columns and then I can easily go thru the data using foreach and display it.

Thanks in advance

Rocky

You can't climb up a ladder with your hands in your pockets.

mcsdgal7-Sep-07 8:21

mcsdgal

7-Sep-07 8:21

I'm using VB.Net 03 and trying to parse a very large document (cannot make smaller). How do I go about using XMLReader (I'm assuming that's what I would use) to parse XML file against XSL file?

Right now I'm having to programmatically split out the file and parse.

murf

Reding xml node in windows Forms [modified]

chakran6-Sep-07 1:10

chakran

6-Sep-07 1:10

Hi,
am working on VS.net 2.0 windows application using c#.
while am reading value of node in xml doc it is giving empty string.pls see the code below. can any one give me the solution where I had done mistake.

XmlTextReader reader = new XmlTextReader(@"C:\book.xml");
while (reader.Read())
{
reader.MoveToElement();
if (reader.Name == "year")
{
label1.Text = reader.Value.ToString();
}
}

book.xml file:
<code<?xml version="1.0" encoding="utf-8" ?="">
<bookstore>
<book category="COOKING">
<title lang="en"> Everyday Italian < /title>

<author>Giada De Laurentiis </author>

<year>2005 </year>
<price>30.00 </price>
</book>

</bookstore>

Thanks

-- modified at 7:22 Thursday 6th September, 2007

Re: Reding xml node in windows Forms

Chetan Patel7-Sep-07 2:39

Chetan Patel

7-Sep-07 2:39

You can directly read the xml file in DataSet

using

ds.ReadXML("xmlfilename.xml");

now you can get each Tag as Columns

Best Regards,
Chetan Patel

Re: Reding xml node in windows Forms

israr Ali .NET7-Sep-07 2:39

israr Ali .NET

7-Sep-07 2:39

XmlTextReader reader = null;
try
{
//Load the reader with the XML file.
reader = new XmlTextReader("c:\\book.xml");

//Parse the XML and display the text content of each of the elements.
while (reader.Read()){
if (reader.IsStartElement()){
if (reader.IsEmptyElement)
Console.WriteLine("<{0}/>", reader.Name);
else{
Console.Write("<{0}> ", reader.Name);
reader.Read(); //Read the start tag.
if (reader.IsStartElement()) //Handle nested elements.
Console.Write("\r\n<{0}>", reader.Name);
Console.WriteLine(reader.ReadString()); //Read the text content of the element.
}
}
}

}

finally
{
if (reader != null)
reader.Close();
}
try this code and remove space in your xml title closing tag in between < and / and put label1.text or what you like instead of Console.WriteLine .

<bookstore>
<book category="COOKING">
<title lang="en"> Everyday Italian !!< /title>!!

<author>Giada De Laurentiis </author>

<year>2005 </year>
<price>30.00 </price>
</book>

</bookstore>

Israr Ali

Calling a template recursively??

Rocky#5-Sep-07 0:23

5-Sep-07 0:23

Hello everyone,

well I want to make this one as simple as I can.
I have an XML inwhich you can get nodes in this type of format

<LOG>
<LogConfiguration>

</LogConfiguration>
<CallSequence>
<Call>
<ObjectType></ObjectType>
<ObjectName></ObjectName>
<Interface></Interface>
<Method></Method>
<ReturnCode></ReturnCode>
</Call>
<Call>
<ObjectType></ObjectType>
<ObjectName></ObjectName>
<Interface></Interface>
<Method></Method>
<Arguments></Arguments>

<CallSequence>
<Call>....</Call>
</CallSequence>
</LOG>

Now what I'm trying to do is to traverse it recursively using just a single template to tranverse both the /LOG/CallSequence/Call and any CallSequence/Call Elements that occur inside it. So can anyone plz give me an idea of how to do this.

I have made a template that traverses the outer part but i dont know how to reach the inside CallSequence/Call part???!!!

Thanks in advance!

Rocky

You can't climb up a ladder with your hands in your pockets.

George L. Jackson5-Sep-07 2:15

5-Sep-07 2:15

Here is an example:

<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/">
<html>
<head>
<title>Call Sequence</title>
</head>
<body>
<xsl:apply-templates select="."/>
</body>
</html>
</xsl:template>
<xsl:template match="CallSequence">
<xsl:for-each select="Call">
<xsl:choose>
<xsl:when test="CallSequence">
<xsl:apply-templates select="CallSequence"/>
</xsl:when>
<xsl:otherwise>

</xsl:otherwise>
</xsl:choose>
</xsl:for-each>
</xsl:template>

</xsl:stylesheet>

"We make a living by what we get, we make a life by what we give." --Winston Churchill

Rocky#5-Sep-07 2:57

5-Sep-07 2:57

That looks preetu helpful but the problem is that the xsl I'm working on is very large and accessing the CallSequence/Call is used at two places. So I wanted to use the same template for both. that is for outer as well the inner occurence. The XML can contain any number of call sequences within a call as u know a method can call another method and that can call yet another one so what i'm trying to do is to develop a template which i can call by passing it the set of nodes. Then it should display it.

by the way if we use xsl:template match="CallSequence"... is it able to get all the CallSequence nodes as we traverse down the tree??

Rocky

You can't climb up a ladder with your hands in your pockets.

Rocky#5-Sep-07 3:05

5-Sep-07 3:05

its giving an error

The XSL processor stack has overflowed - probable cause is infinite template recursion

what should be the termination condition in this?

Rocky

You can't climb up a ladder with your hands in your pockets.

George L. Jackson5-Sep-07 5:56

5-Sep-07 5:56

<xsl:apply-templates select="CallSequence"/> is the recursive call and will be called if "CallSequence" is a child of itself at any point. If you call this more than once within your xsl:for-each loop, you will run out of stack. Also, it should return once it does not find another child "CallSequence"; however, if your xsl:for-each does not account for a recursive call, it will cause an out-of stack error also. It is very hard to troubleshoot a large template with nested xsl:for-each loops. I advise you to break up your code into several templates. XSLT is functional in nature and you should keep nested levels of xsl:for-each to a minimum.

"We make a living by what we get, we make a life by what we give." --Winston Churchill

Rocky#5-Sep-07 18:53

5-Sep-07 18:53

OK that looks helpful to me! Please tell what this statement is doing

<xsl:apply-templates select="."/>

in the example code you've given, When I changed the . to CallSequence it doesnt show anything (atleast the error is gone) but when i put this as you have given it runs out of stack. right now I'm just trying to run your code in order to make an understanding of the template I wanna make at the moment. After I'm done with this I'll concentrate on embedding it in the whole this as a sepearte function like you said

Rocky

You can't climb up a ladder with your hands in your pockets.

George L. Jackson6-Sep-07 1:50

6-Sep-07 1:50

Sorry, my mistake. The "." means current node. It should be "CallSequence".

"We make a living by what we get, we make a life by what we give." --Winston Churchill

Rocky#5-Sep-07 19:50

5-Sep-07 19:50

well now I've changed the <xsl:apply-templates select="."/> to
<xsl:apply-templates select="*"/>
and its showing the output BUT... as I was thinking... the Call Node that has other CallSequence nodes is comming out at the end bcz of the stack. Actually the calling function should come at the top rather than at the bottom.

Right now I'm thinking abt another way around. How abt if I use a template to display the Nodes inside a Call and if there is yet another CallSequence I call that template again (using Call-template) with the new Node Set.

Rocky

You can't climb up a ladder with your hands in your pockets.

Rocky#6-Sep-07 1:30

6-Sep-07 1:30

<xsl:template name="CallSequenceTemplate">
<xsl:param name="nodeset"/>
<xsl:for-each select="msxsl:node-set($nodeset)/CallSequence/Call">
<table>
<br/>
<tr>
<td class='heading3'><b>Call to <xsl:value-of select="Method"/></b></td>
</tr>
</table>
<table width="100%">
<tr><td width="10%">Object Type </td><td><i><xsl:value-of select="ObjectType"/></i></td></tr>
<tr><td>Object Name </td><td><i><xsl:value-of select="ObjectName"/></i></td></tr>
<tr><td>Interface Name </td><td><i><xsl:value-of select="Interface"/></i></td></tr>
<tr><td>Return Code </td><td><i><xsl:value-of select="ReturnCode"/></i></td></tr>

</table>
<xsl:for-each select="Arguments">
<table width = "100%" border="0" class="border" cellpadding="0" cellspacing="1">
<tr><td class='heading4'> </td></tr>

<xsl:if test="Results/Value">
<tr class="nonSelectedRow">
<td colspan="6" class = 'detail_table_element'><b>Inputs</b></td>
</tr>
</xsl:if>
<xsl:if test="Results/Compound">
<tr class="nonSelectedRow">
<td colspan="4" class = 'detail_table_element'><b>Inputs</b></td>
<td colspan="2" class = 'detail_table_element'><b>Output</b></td>
</tr>
</xsl:if>
<tr class="nonSelectedRow">

<xsl:for-each select="*[name() != 'Results'] | Results/child::node()[1] | Results/child::node()[1] / child::node()[2]">
<th><xsl:value-of select="name()"/></th>
</xsl:for-each>
</tr>
<tr>
<xsl:for-each select="*[node() and name() != 'Results']">
<td valign = "top"><xsl:value-of select="node()"/></td>
</xsl:for-each>

<xsl:if test="Results/Compound">
<td>
<table border="0" width = "100%">
<xsl:for-each select="Results/Compound">
<tr>
<td><xsl:value-of select="Name"/></td>
</tr>
</xsl:for-each>
</table>
</td>
<td>
<table border="0" width = "100%">
<xsl:for-each select="Results/Compound">
<tr>
<td><xsl:value-of select="Value"/></td>
</tr>
</xsl:for-each>
</table>
</td>
</xsl:if>

<xsl:if test="Results/Value">
<xsl:for-each select="Results">
<td><xsl:value-of select="Value"/></td>
</xsl:for-each>
</xsl:if>
</tr>
</table>
</xsl:for-each>
</xsl:for-each>
</xsl:template>

-----------------

I've almost done it!! the calling doesnt go to the third level so I call it this way...

<xsl:call-template name="CallSequenceTemplate">
<xsl:with-param name="nodeset" select="/LOG"/>
</xsl:call-template>
<xsl:call-template name="CallSequenceTemplate">

<xsl:with-param name="nodeset" select="/LOG/CallSequence/Call"/>
</xsl:call-template>

The only problem now is that as its taking All the call which are at the same level. It ignores the sequence of call for example when a method is called after lots of nested calls in a previous method.

Thanks very much u know I really appreciate your effort. I wouldnt have done this with out u.

Thanks!

Rocky

You can't climb up a ladder with your hands in your pockets.

George L. Jackson6-Sep-07 1:54

6-Sep-07 1:54

You just have to remember that xsl:call-template works with the current node and doesn't change scope like xsl:apply-templates. Also, xsl:apply-templates has a mode attribute that is used to name it like xsl:call-templates and you can pass parameters to it also.

"We make a living by what we get, we make a life by what we give." --Winston Churchill

Rocky#6-Sep-07 2:17

6-Sep-07 2:17

wht does it mean when we say that call-template doesnt change scope? bcz after this statement the xsl:template gets called right? so we can change the scope inside the template right?

Rocky

You can't climb up a ladder with your hands in your pockets.

George L. Jackson6-Sep-07 2:25

6-Sep-07 2:25

xsl:call-template has is own "scope" as far as variable creation. But the scope of the current node and node-list is the same as its calling parent.

"We make a living by what we get, we make a life by what we give." --Winston Churchill

Rocky#6-Sep-07 2:33

6-Sep-07 2:33

OK! can u tel me how can we get the parent node of the current node.
<xsl:if test="name()='CallSequence'">
<xsl:apply-templates select="parent()"/>
</xsl:if>

I was thinking that while traversing through the $nodeset I shoujld chk for the existance of another CallSequence Node and the call the same template again recursively.

Rocky

You can't climb up a ladder with your hands in your pockets.

George L. Jackson6-Sep-07 2:41