|
Well, first I gotta ask if there's a typo in your input XML. The end tag for the document element doesn't match. The next thing I'd like to know is what is the error you're getting? Do you get the error when you load the document, when you put it in the data document, or when you run the transform?
|
|
|
|
|
Sorry. Here is the correct XML:
<?xml version="1.0" encoding="UTF-8"?>
<itemlist xmlns="urn:ahw:itemlist">
<item name="Photos" friendly-name="Photos" />
<item name="Videos" friendly-name="Videos" />
<item name="OtherMedia" friendly-name="Other Media" />
</itemlist>
I'm not getting an error. Its just nothing appears on page.
|
|
|
|
|
Try putting two slashes before itemlist: <xsl:template match="//itemlist">
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." - Rick Cook www.troschuetz.de
|
|
|
|
|
sorry but that had no impact.
Thanks for the quick replies!
|
|
|
|
|
I got it working now!!!
Heres is what I needed to change in the XSL:
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:t="urn:ahw:itemlist"
exclude-result-prefixes="t">
<xsl:template match="t:itemlist">
<TABLE BORDER="2">
<TR>
<TD>Display Name</TD>
<TD>Name</TD>
</TR>
<xsl:for-each select="t:item">
<TR>
<TD><xsl:value-of select="@friendly-name"/></TD>
<TD><xsl:value-of select="@name"/></TD>
</TR>
</xsl:for-each>
</TABLE>
</xsl:template>
</xsl:stylesheet>
|
|
|
|
|
Ah the namespace. Of course. Should have seen that 
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." - Rick Cook www.troschuetz.de
|
|
|
|
|
Hi,
I know Xml is used in FlashPlayer,but i dont have acurate idea of Xml in flash.Can anyone help me???????
Thanks in advance
Siddharth
|
|
|
|
|
hi,
How to display XML document in the Standard RSS 2.0 format in asp.net?
I am writing XML through Dataset but it is not in the format of RSS 2.0.
How I should convert this XML in RSS 2.0 format so that it can be readable by any RSS news reader.
I want a tag related to <rss version="2.0"> instead of <newdataset> and <channel> instead of
My code snippet is as follows:
<newdataset>
<title>fgdhfgjkhdf<>@#%#%%#%&*&)&){}gggg'jkk;<ghghgjgh>
<shopid>84
~\Images\Banner\grocery.jpg<description>Royal Gift
<pubdate>2007-01-10T14:28:34+05:30
<productid>191
<description1>This is good for health
<link1>~/Images/ProductImage/CA1CJ94A.jpg
<title>Ashoka Mall
<shopid>85
~\Images\Banner\lipsticks.jpg<description>asdasd
<pubdate>2007-01-10T16:30:34+05:30
<productid>192
<description1>asdsad
<link1>~/Images/ProductImage/CAOLEV45.jpg
Please guide .
Thank you.
yog
hui gfgh kgdgrt njjn hjgkn
|
|
|
|
|
Hi,
i am working on asp. i am new to .Net technology & xml.i am trying to learn .net technology.
my question is where can we use xml in our project?? i mean when i think of using xml, i am not getting any ideas.i have gone thru xml (from w3schools.com). when i read the topics, i am understanding the topics, but when i want to implement them in my sample project (it's a just simple banking application. which deals with opening accounts and managing accounts...)
any suggestions please..................
thanks,
Rahi
If you look at what you do not have in life, you don't have anything,
If you look at what you have in life, you have everything... "
|
|
|
|
|
IMHO, XML is basically a readible hierarchical data container in a text document. Optionally, you can enforce its structure and data types using a schema. You have several methods of reading, updating, creating and transforming this data using DOM, XSLT, and push and pull streaming.
Using XML with a banking application is possible. However, you have to be aware of security issues that will come up.
"We make a living by what we get, we make a life by what we give." --Winston Churchill
|
|
|
|
|
hi George,
thanks for the response. please can u guide me where and how can i use in my application(sample Banking). just i need the idea to implement the technology.
Thanks,
Rahi
If you look at what you do not have in life, you don't have anything,
If you look at what you have in life, you have everything... "
|
|
|
|
|
I cannot answer where and how since I don't know your application's requirements. XML is a generic technology, and I don't have the time to list all of its possible uses that you may entertain. Nevertheless, the .NET Framework uses a lot of XML technologies. For example, a dataset object relies on XML technology for database activities on and off-line.
"We make a living by what we get, we make a life by what we give." --Winston Churchill
|
|
|
|
|
thanks once again for ur response. yeah! u r correct. it's a vast subject and u don't have any idea about the application. i will try to findout other way.
Thanks,
Rahi
If you look at what you do not have in life, you don't have anything,
If you look at what you have in life, you have everything... "
|
|
|
|
|
Hi Rahi,
Just like you, I'm new to .NET and had a similar question a couple of months ago. While I will not be able to provide a comprehensive answer as to when and where to use XML, I can tell what I've done with it, and maybe it'll help you see one of its uses. I've been working on the client side of an application that uses web services provided by a number of search engines. Before the user can start querying the search engines, he needs to specify some data, such as the names of the supported seach engines to use, the number of queries to submit per engine, the names of the files containing the queries, etc. Squeezing all these options into one interface along with the actual "start-stop-search feature" would make for a busy-looking GUI, especially since the ultimate client does not need to have access to all these options all the time--only to the start-stop-search feature and an options file containing all that info. So as not to hardcode the search options, I split the application in two: if the user has an options file (with all these options set), he can simply specify it in the dialog box and click the "Start Search" button. If there is no such file, he can click on the menu option that starts the other form with the GUI allowing him to fill in the data and create an options file. I use XML to store the data created by the options builder form into the options file. When the user specifies the options file (containing all this data); he only sees a very simple GUI, where he needs to specify the location of the options file and click the "Start Search" button. While the user doesn't mess with XML at all, the application does, since the format helps it access the data in a more organized manner, where I can extract the relevant data, say for the number of queries for Google, Yahoo, or MSN by extracting the data in the options file stored under the tag of "GoogleQueries", "YahooQueries", or "MSNQueries". Hope this makes it a little clearer for you. If not, you may want to grab a book (I used "C# Programming") and take a look at the examples given there.
Vladimir
|
|
|
|
|
Thanks for ur response. i got to know some what but u know to be frank i need some more information to apply XML techonolgy in my sample project. please can u tell me the author and publications for C# Programming book where i can find the examples?
Thanks once again for ur response,
Rahi
If you look at what you do not have in life, you don't have anything,
If you look at what you have in life, you have everything... "
|
|
|
|
|
You can check out "C# Cookbook" written by Jay Hilyard and Stephen Teilhet: there are a lot of useful examples there. Perhaps, you'll be able to find something that'll suit you.
Good luck!
Vladimir
|
|
|
|
|
Hi Shakhtyor,
Thanks for letting me know about this Book!
Thanks,
Rahi
If you look at what you do not have in life, you don't have anything,
If you look at what you have in life, you have everything... "
|
|
|
|
|
Hi,
I am new to XSL and I was hoping someone could help me with a problem I am having.
I have an Input.xml file to which I want to apply a xsl stylesheet Style.xsl. I also have a Template.xml file which I want to use as the base for the output file.
At the moment, here is what I have:
<!-- Input.xml -->
<?xml version="1.0" encoding="UTF-8"?>
<InputRoot>
<elem name="a" AttName='11'></elem>
<elem name="b" AttName='22'></elem>
<elem name="c" AttName='33'></elem>
<elem name="d" AttName='44'></elem>
<elem name="e" AttName='55'></elem>
<elem name="f" AttName='66'></elem>
</InputRoot>
<!-- Template.xml -->
<?xml version="1.0" encoding="UTF-8"?>
<TemplateRoot>
<elem name="a" AttName='Ones'></elem>
<elem name="b" AttName='Twos'></elem>
<elem name="c" AttName='Threes'></elem>
<elem name="d" AttName='Fours'></elem>
<elem name="e" AttName='Fives'></elem>
<elem name="f" AttName='Sixes'></elem>
</TemplateRoot>
<!-- Style.xsl -->
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
<xsl:variable name="Template" select="document('Template.xml')"/>
<xsl:template match="@* | node()">
<xsl:copy>
<xsl:apply-templates select="@* | node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="elem">
<xsl:variable name="iden" select="@name"/>
<xsl:variable name="attrVal" select="@AttName"/>
<xsl:variable name="newAttrName" select="$Template/TemplateRoot/elem[@name =$iden]/@AttName"/>
<xsl:element name="elem">
<xsl:attribute name="name">
<xsl:value-of select="@name"/>
</xsl:attribute>
<xsl:attribute name="{$newAttrName}">
<xsl:value-of select="$attrVal" />
</xsl:attribute>
</xsl:element>
</xsl:template>
</xsl:stylesheet>
<!-- Output.xml -->
<?xml version="1.0" encoding="UTF-8"?>
<InputRoot>
<elem name="a" Ones="11"/>
<elem name="b" Twos="22"/>
<elem name="c" Threes="33"/>
<elem name="d" Fours="44"/>
<elem name="e" Fives="55"/>
<elem name="f" Sixes="66"/>
</InputRoot>
I seem to be doing this backwards, here is what I want
<!-- Desired Output.xml -->
<?xml version="1.0" encoding="UTF-8"?>
<TemplateRoot>
<elem name="a" Ones="11"/>
<elem name="b" Twos="22"/>
<elem name="c" Threes="33"/>
<elem name="d" Fours="44"/>
<elem name="e" Fives="55"/>
<elem name="f" Sixes="66"/>
</TemplateRoot>
Any help would be greatly appreciated
-----------------
Genaro
|
|
|
|
|
picazo wrote: I have an Input.xml file to which I want to apply a xsl stylesheet Style.xsl. I also have a Template.xml file which I want to use as the base for the output file.
So you are trying to use 2 XML files in the XSLT right? There may be support for that in XSLT 2.0 I am not sure. Even if there is there may not be an engine that supports it yet, I don't know. However:
picazo wrote: I also have a Template.xml file which I want to use as the base for the output
That is what the XSLT is for so you may just be over complicating your solution. You should only need the XSLT file and a single XML input file.
led mike
|
|
|
|
|
picazo wrote:
<xsl:template match="@* | node()">
<xsl:copy>
<xsl:apply-templates select="@* | node()"/>
</xsl:copy>
</xsl:template>
This code is really your problem. You should try matching differently. Instead of doing this, try replacing it with:
<xsl:template match="/">
<TemplateRoot>
<xsl:for-each select="InputRoot/elem">
<xsl:apply-templates select="."/>
</xsl:for-each>
</TemplateRoot>
</xsl:template>
The code may not be exactly correct because I was too lazy to test it. I think it's a neat idea to mix two XML files, but it depends on your requirements. In most cases, you would want to adjust the XSL instead of having a template XML file outside, like led mike suggested.
|
|
|
|
|
Hi guys,
I've only ever worked with XML, never really designed, so I'm looking for a little advice. I need to design four request message types (and corresponding replies, but that later). I would like to use a standard enclosing document, with a message type attribute or element that then defines how the recipient must treat the rest of the message. I don't know where to start, what guidelines to use for structure, where attributes and where elements etc. Any advice and tips will be appreciated.
|
|
|
|
|
Try searching for "XML Schema Best Practices".
"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." - Rick Cook www.troschuetz.de
|
|
|
|
|
Brady Kelly wrote: I don't know where to start
Representing data in XML is not that far removed from traditional programming. Design your data just as you would in a C structure. Now that structure can be mostly mirrored in XML.
Brady Kelly wrote: I would like to use a standard enclosing document, with a message type attribute or element that then defines how the recipient must treat the rest of the message
Take a look at the high level design of SOAP.
Brady Kelly wrote: where attributes and where elements etc
There is no cookbook approach. The best advice would be to NOT mix "actual data". Meaning don't put some data in text nodes and others in attributes. So if you use text nodes for data then attribute usage should be limited to Metadata usage. Conversely if you are going to have much metadata then using text nodes for the real data might make the XML more readable.
I hope that helps at least a little 
led mike
|
|
|
|
|
HELP EACH OTHER TO GROW TOGETHER.
|
|
|
|
|
You should post a question or an issue if you want an answer.
"We make a living by what we get, we make a life by what we give." --Winston Churchill
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
