|
hiraljv wrote: 6lacs (or More) pages
what is "6lacs"?
hiraljv wrote: as our client dont want xml and xslt.
Then let the client do it themselves thier own way. If they want you to do it they don't tell you "how" to do it.
hiraljv wrote: 1) Faster Report Generation
Faster than what?
hiraljv wrote: 3) Export and Import of repots for other popular formats
Import a report? Never heard of that, normally you import the "data" used in the report, you don't import the report.
led mike
|
|
|
|
|
can attributes be null??????
|
|
|
|
|
not exactly if you will have like this
<rizwan att1="hello">
and
<rizwan>
then on accessing Second attribute you will get ("") blank stirng.
|
|
|
|
|
|
not exactly if you will have like this
<Rizwan att1="hello">
and
<Rizwan>
then on accessing Second attribute you will get ("") blank stirng.
Rizwan Bashir
ALM Soft[^]
|
|
|
|
|
can u make it more clear please
|
|
|
|
|
I have an existing application I'm trying to support, and am having some troubles. I'm not too familiar with XML/XSL. Here's the situation.
I am trying to put a value from a querystring into a hidden form element using xsl. where the url is object.asp?candidateID=285
there is an asp file that looks like it creates the xml file. Inside that file there is this code:
for each item in request.queryString
proc.addParameter cstr(item), cstr(request.queryString(item))
next
I'm assuming this creates an xml object somewhere that I can reference.
Inside my xsl file I am trying to reference it this way:
But it is not returning a value.
Any help on this would be greatly appreciated. It's driving me nuts...
|
|
|
|
|
The XSL is not going to be able to read that. You should try something like:
<input type="hidden" name="candidateID">
<xsl:attribute name="value">
<xsl:value-of select="@candidateID" />
</xsl:attribute>
</input>
Logifusion[^]
If not entertaining, write your Congressman.
|
|
|
|
|
When I view the source this is al I get.
So for some reason it's not picking up the value from the url.
|
|
|
|
|
Well, it's selecting @candidateID. That would have to be an attribute of the current node. I have no idea what the current node is when this code is run. You really just have to check the code before it to see where the XSL processor is in regards to the XML file. If you need help, you can always post more of your XSL and a sample of the XML you're parsing.
Logifusion[^]
If not entertaining, write your Congressman.
|
|
|
|
|
the xml looks like this:
- <survey id="DFSCRFKPY5dAM4UJAIP1" style="/adeptiv/survey/assets/templates/none.xsl">
<name>Test2
<description>
- <questions>
<question id="a3eDT0NR7ZcYYKRNQ05d" type="field" number="1" depth="1" required="false" value="How old are you" answer="">
- <question id="FNDL0YhGVg5aK3PZdOb6" type="pulldown" number="2" depth="1" required="false" value="Where do you live" answer="">
PA
VT
- <question id="X2M7aO1D4b1RMcSXWQB4" type="radio" number="3" depth="1" required="false" value="how important is Apple Pie?" answer="">
1
2
3
4
5
So I don't even see the candidateID in there.
The xml is being generated by and asp page. which contains this code:
set selection = xmlDoc.selectSingleNode(path)
if typename(selection) <> "Nothing" then
style = selection.text
set xslDoc = load(style)
xsltDoc.stylesheet = xslDoc
set proc = xsltDoc.createProcessor()
proc.input = xmlDoc
for each item in request.queryString
proc.addParameter cstr(item), cstr(request.queryString(item))
next
for each item in request.form
proc.addParameter cstr(item), cstr(request.form(item))
next
for each item in request.serverVariables
proc.addParameter cstr(lcase(item)), cstr(request.serverVariables(item))
next
I was thinking because it looks like it loops through the query string, it should be creating something in the xml that I could reference. I just don't see it.
Thanks so much for looking at this!
|
|
|
|
|
I can't quite see all your XML. Did you use the check box to ignore html tags? Anyways, if candidateID is not an attribute in there, then it certainly won't show up in your input tag. But, what you're looking at with proc.addParameter is that a parameter is being passed into the XSL for processing. Up at the top of the XSL should be a xsl:param tag for candidateID if that is indeed one of the items in the querystring or form. To access it use $candidateID instead of @candidateID. The $ is used for variables and the @ is used for attributes.
Logifusion[^]
If not entertaining, write your Congressman.
|
|
|
|
|
BEAUTIFUL!! It works! Thanks so much!
|
|
|
|
|
Anybode have done like:
Node BOOK1 in a GroupBox and all the inner nodes(title1,author1 etc...) as an LABEL inside the node BOOK1.New GroupBox for BOOK2 and same for that...Please help....
<bookstore>
<book1 genre1="autobiography" publicationdate1="1981" ISBN1="1-861003-11-0">
<title1>The Autobiography of Benjamin Franklin</title1>
<author1>
<first-name1>Benjamin</first-name1>
<last-name1>Franklin</last-name1>
</author1>
<price1>8.99</price1>
</book1>
<book2 genre2="novel" publicationdate2="1967" ISBN2="0-201-63361-2">
<title2>The Confidence Man</title2>
<author2>
<first-name2>Herman</first-name2>
<last-name2>Melville</last-name2>
</author2>
<price2>11.99</price2>
</book2>
</bookstore>
fghfhgfgcncnb
|
|
|
|
|
To the point, I want to create a table on class XML summary comment. Well I want to create the table because I want to use NDoc to build the documentation of the class of my library. But I don't know how to create it. The table is static not load data on database (SQL, MySQL, etc.) it just like this :
Can anyone help me, please.
Regards,
Ariston Darmayuda.
|
|
|
|
|
You can use a list:
<summary>
This is a table.
<list type="table">
<listheader>
<term>Col A</term>
<term>Col B</term>
</listheader>
<item>
<description>1</description>
<description>2</description>
</item>
<item>
<description>3</description>
<description>4</description>
</item>
</list>
</summary>
Logifusion[^]
If not entertaining, write your Congressman.
|
|
|
|
|
Hi, I have a xml string that I have to parse. I am using xpath to parse this string. I can get to the part <b>A1:ABCID="4567"</b> but when I try to access <b>A2:parentid="0123"</b>. It doens't let me.
can some help me out with the syntax example?
thanks
XML string is:
<?xml version="1.0" encoding="utf-16"?>
<A1:MyName A1:ABCID="4567" A2:parentid="0123"
xmlns:A2="http://abc.cdf.com/MySubscription/SinIN/2006/response"
xmlns:A1="http://abc.cdf.com/MySubscription/SinIN/2005/response>"
<A1:Necessities>"
<A1:Necessity A1:ID="3" />"
</A1:Necessities>"
</A1:MyName>"
-- modified at 10:22 Tuesday 8th August, 2006
Thanks
Needy
|
|
|
|
|
Hi,
I need to add, remove or make optional, some elements based on the values of an attribute of the parent element.
I have an element "report" that has an attribute "investortype", which can have 3 possible values: "none", "indvidual" and "group".
Now what i need is, to create/modify elements in the report element based on these 3 values. The following example will elaborate:
investortype = "individual"
---------------------------
<report
reportname="ABCD"
destinationdir="C:\XSD"
outputfilename="$DATE1$-ABCD.txt"
investortype="none">
<!-- Both elements below should be Optional-->
<investorcode code="316" />
<investorrange start="316" end="317"/>
</report>
investortype = "group"
---------------------------
<report
reportname="ABCD"
destinationdir="C:\XSD"
outputfilename="$DATE1$-ABCD.txt"
investortype="none">
<!-- Atleast one of the two is required -->
<investorcode code="316" />
<investorrange start="316" end="317" />
</report>
investortype = "none"
---------------------
<report
reportname="ABCD"
destinationdir="C:\XSD"
outputfilename="$DATE1$-ABCD.txt"
investortype="none">
<!-- None of the 2 should be present -->
</report>
Any help or hint would be great. Also i need to know if this is even possible in XSD?
Awaiting reply and Thanx in advance
☺«««DTA»»»☺
|
|
|
|
|
hi there,
I used to place a meta refresh (forwarding to a page explaining that javascript is required) within a noscript tags in my header. it looked like this and worked fine:
<head>
... stuff here...
<noscript>
<meta http-equiv="refresh" content="0;url=myerrorpage.aspx" />
</noscript>
</head>
but nowadays I swim with the river and try to be standards complient. I use the w3c validators to validate my xhtml. it throws an error because it doesn't like the noscript tags. I wonder how I can check wether the clientbrowser supports javascript with this limitation.
how do you folks do it?
thanks in advance!
/matthias
I love deadlines. I like the whooshing sound they make as they fly by. [Douglas Adams]
|
|
|
|
|
So if the user doesn't support javascript, what do you want to do?
/\ |_ E X E GG
|
|
|
|
|
hi eggie,
thanks for your reply. in case the client browser does not support javascript or has javascript disabled, i want to send him to a specific page where he gets some information about the basic requirements to access the site.
regards!
/matthias
I love deadlines. I like the whooshing sound they make as they fly by.
[Douglas Adams]
|
|
|
|
|
Hi
I am now using xlst to write out my xml doc as a HTML string instead of using selectnode etc. It's neat. But....I can't work out how to specify search criteria for the xml doc. I just get it all. Sample below :-
XML DOC
<Fields>
<BatchParam name="Field 1" tab="Tab 1" Seq="1" />
<BatchParam name="Field 2" tab="Tab 1" Seq="3" />
<BatchParam name="Field 3" tab="Tab 1" Seq="2" />
<BatchParam name="Field 1" tab="Tab 2" Seq="1" />
<BatchParam name="Field 2" tab="Tab 2" Seq="3" />
<BatchParam name="Field 3" tab="Tab 2" Seq="2" />
<BatchParam name="Field 1" tab="Tab 3" Seq="1" />
</Fields>
I want to display a specific tab, eg Tab 2 in a table, ordered by seq
My XSL
<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match='/ | @* | node()'>
<xsl:copy>
<xsl:apply-templates select="node()">
<xsl:sort select='@seq'/>
</xsl:apply-templates>
</xsl:copy>
<tr>
<td>
<xsl:value-of select='position()'/>
</td>
<td>
<xsl:value-of select='@tab'/>
</td>
<td>
<xsl:value-of select='@name'/>
</td>
<td>
<xsl:value-of select='@seq'/>
<br/>
</td>
</tr>
</xsl:template>
</xsl:stylesheet>
and finally my C# code
System.IO.StringWriter objStream = new System.IO.StringWriter();
System.Xml.Xsl.XslTransform objTransform = new System.Xml.Xsl.XslTransform();
objTransform.Load(madconfig.Config.Get("MYXSLFILE.XSL"));
System.Xml.XPath.XPathDocument xml = new System.Xml.XPath.XPathDocument("MYXMLFILE.XML");
System.Xml.XPath.XPathNavigator xmlNav = xml.CreateNavigator();
objTransform.Transform(xmlNav, null, objStream, null);
Response.Write ("<table border=1>"+objStream.ToString()+"</table>");
And this displays ALL the entries. Before, rolling my own I did something like
string tabName = GetTabName();
System.Xml.XPath.XPathExpression expr = xmlNav.Compile("/Fields/BatchParam[@name=\""+tabName+"\"]");
System.Xml.XPath.XPathNodeIterator iterator = xmlNav.Select(expr);
Any ideas...?
Regards
Angel
*********************************************
The sooner you fall behind, the longer you have to catch up.
|
|
|
|
|
So...you can pass parameters down. But I am still struggling. This is where I am now...
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:param name="tabName" select="Main"></xsl:param> <-- MY PARAM
<xsl:template match="Fields">
<table border="3">
<xsl:copy>
<xsl:apply-templates select="BatchParam">
<xsl:sort select='@tab'/>
<xsl:sort select='@seq'/>
</xsl:apply-templates>
</xsl:copy>
</table>
</xsl:template>
<xsl:template match="BatchParam[@tab='Main']"> <-- WHERE I WANT TO USE IT
<tr>
<td><xsl:value-of select='position()'/></td>
<td><xsl:value-of select='@tab'/></td>
<td><xsl:value-of select='@name'/></td>
<td><xsl:value-of select='@seq'/></td>
</tr>
</xsl:template>
</xsl:stylesheet>
If I replace the hardcoded 'Main' with the param as in
<xsl:template match="BatchParam[@tab=$tabName]">
I get an exception...
System.Xml.XPath.XPathException: 'BatchParam[@tab=$tabName]' is an invalid key pattern. It either contains a variable reference or 'key()' function.
Help!!!!
Regards
<strike>Angel</strike>Malcolm
*********************************************
The sooner you fall behind, the longer you have to catch up.
|
|
|
|
|
Malcolm Smart wrote: <xsl:param name="tabName" select="Main"></xsl:param>
This line is a little odd. This is a template parameter, not a variable. The difference is that you're supposed to be passing this parameter in when you call the stylesheet. There are also parameters for template matching sections. You can put a variable instead:
<xsl:variable name="tabName"></xsl:variable>
Also, your select is not going to put the string 'Main' into tabName. It's going to try and find a node called Main and put it there. You could stick text into it if you want:
<xsl:variable name="tabName"><xsl:text>Main</xsl:text></xsl:variable>
As for your XPath statement, I'm unsure why it gave you that error. Try changing to a variable with text and see how it reacts.
Logifusion[^]
If not entertaining, write your Congressman.
|
|
|
|
|
Hi Thanks for the info...still no joy (and I am trying - have been all ****** afternoon...)
Overall reqs are - use select tab from front end. I extract just the nodes which have the tab attribute set to this tab. So a) I need to be able to pass the tab name down from the front end into the xsl and b) use it in teh xsl. I am still struggling with b) and not even looked at a) yet!!
My code now, with your changes, still gives the exception....I need a little more hand holding. This is my first venture into XSL and really struggling, both conceptually, and syntactically.
<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:variable name="tabName">
<xsl:text>Main</xsl:text>
</xsl:variable> <xsl:template match="Fields">
<table border="3">
<xsl:copy>
<xsl:apply-templates select="BatchParam">
<xsl:sort select='@tab'/>
<xsl:sort select='@seq'/>
</xsl:apply-templates>
</xsl:copy>
</table>
</xsl:template>
<xsl:template match="BatchParam[@tab=$tabName]"> <tr>
<td><xsl:value-of select='position()'/></td>
<td><xsl:value-of select='@tab'/></td>
<td><xsl:value-of select='@name'/></td>
<td><xsl:value-of select='@seq'/></td>
</tr>
</xsl:template>
</xsl:stylesheet>
It still doesn't like the $tabName. VS2005 highlights it as a problem in the editor before i run it!
Regards
AngelMalc
*********************************************
The sooner you fall behind, the longer you have to catch up.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
