Deepak Bala wrote:xsl variable mixed with a c:set JSP file ?
XSL commands are part of a XSLT process. I am not sure I understand your question. How are the XML / XSLT / JSP files related ?
Deepak Bala wrote:Is this a XML file ?
My best guess is that a XSL transformation rule runs on a XML file to produce a JSP which contains the c:set element. Is that the case ?
Deepak Bala wrote:I think the best thing to do is to step back and look at what you want to do.
You have a XML file that a XSLT works on a to give an output file. Is this output file a JSP or HTML ? What is your requirement ?
The output is in html to my understanding.
Deepak Bala wrote:
The output is in html to my understanding.
Cool. So what is the nature of the change that you want to make to this file ? Someone requested new data to become available in the view ?
SCJP 91%, SCWCD 97%
Shashank Ag wrote:Well Rob I am assuming here you are completely newbee, so I am stating some fundamentals here:
1. XSL is used as template to generate html document.
In XSL you have various place holders which specify dynamic data.
Now to use this template, a XML is mapped upon XSL for this tag hirarchy XML should correspond to XSL place holders.
The combined output is html. This whole api is availble in J2SE only, so you can generate html pages out of desktop application.
2. JSP technology is based upon java servlet api. It acts as template to produce html. It is part of J2EE.
Well, uptil here they seem to be compareable in terms of end result. But, they do not mix/gel togather as purposes of each is different.
A JSP/Servlet is equipped with servlet lifecycle. It has all the fundamental specifications to be developed as a full fleged, dynamic web application.
While, XSL is only for smaller roles like generating a html report from application or likewise.
In short below will nerver gel togather.
<xsl:variable name="test" select="description"/>
<c:set var="message" value="${test}" />
Don't get me started about those stupid light bulbs. |