Ted Husted wrote:
> What I'm working on now is converting the package.html's to
> package.xml's, so we can generate an overview for the Javadoc and a
> section for the user's guide from the same XML source, same as the TLDs
So I'm having some trouble finding a good way to "include" various
well-formed data sources when building our HTMLs.
I got it to work using entities like
<!DOCTYPE xsl:stylesheet [
<!ENTITY package SYSTEM "package-html.xml">
]>
// ...
&package;
but then it chokes if I try to include the use XLM headers, so the
document can be used on its own.
I've also tried this
<xsl:variable name="package">package.xml</xsl:variable>
// ...
<xsl:template match="body">
<xsl:apply-templates select="document($package)"/>
</xsl:template>
which compiles when package.xml is well-formed, but just outputs the XSL
tags again.
I'm still just "banging the rocks together" when it comes to XML/XLS.
Any ideas, hints?
-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Custom Software ~ Technical Services.
-- Tel +1 716 737-3463
-- http://www.husted.com/about/struts/
