Performance xsql:xml-include vs. xsl:document(...) !

Question

Dear Steve,
I have html markup file stored in XHTML format which is, of
course, XML. Also, I put <marker id="some_name"/> in all places
where I want XSLT injections.
My XSLT is something like this:
<?xml version="1.0"?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="html" indent="yes"/>
<xsl:variable name="markup" select="document('MyMarkup.xml',/)"/>
<xsl:template match="@* | node()">
<xsl:copy>
<xsl:apply-templates select="@* | node()"/>
</xsl:copy>
</xsl:template>
<xsl:template match="/">
<xsl:for-each select="$markup">
<xsl:apply-templates select="html"/>
</xsl:for-each>
</xsl:template>
<xsl:template match="html">
<xsl:copy>
<xsl:copy-of select="@*"/>
<xsl:apply-templates/>
</xsl:copy>
</xsl:template>
<xsl:template match="markup[@id='script']">
<!-- do something here -->
</xsl:template>
</xsl:stylesheet>
Now, here is the question. What is most efficient way to use
this Markup technique?
Is it <xsql:include-xml href=MyMarkup.xml/> in XSQL page
and XSL processing the composite document or xsl:document
function as I described?
What is cached by XSQL servlet, if anything?
The "markup" technique provides clear separation of labor and
layers.
And it is crucial to have it perform well. I think, that it
would be very easy to cache xsql:include-xml document once and
for all sessions or have a special attribute in this tag to
explicitly ask for this.
Sincerely,
David

Answer 1

( I can't use
<xml:transform>
because this expects the xsl file as a parameter )But you know the name of the xsl file, so that shouldn't be a problem, correct...?
But as to your question, the xml file is a static file, so the jsp:include will copy its contents (it acts like <%@ import %> in this case...). The jsp will only process the page if it detects it as a dynamic page, ie Servlet or JSP.
Perhaps you can make an intermediary JSP that transforms the xml... I have never tried it, but would:
//Intermediary JSP:
<jsp:forward page="./stocks2.xml" />
//then in the primary JSP
<jsp:include page="./intermediary.jsp"/>It might fool the jsp:include into thinking the content is dynamic, while the jsp:forward would take care of processing the XML. That assumes that once the jsp:forward is done that the rest of the primary jsp will be handled... not sure if that is the case though...