forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeff Turner <>
Subject Re: New live site: Apache XML Security
Date Fri, 28 Mar 2003 14:02:27 GMT
On Fri, Mar 28, 2003 at 11:25:41AM +0100, Karel Wouters wrote:
> Hi,
> The Apache XML security project moved to Forrest.

cool :)

> (the ugly logo will be replaced as soon as we find some inspiration :)
> Here's some feedback:
> - We have multiple FAQ files, named faq.xml in different directories and
>   when producing the PDF for those files, we get nullpointerexceptions:

Oops, yes that's a bug, which I've just fixed.

For the xml-security site, you can get this fix by overriding the default
Forrest sitemap, and instead using a version with this patch:

Index: sitemap.xmap
RCS file: /home/cvs/xml-forrest/src/resources/conf/sitemap.xmap,v
retrieving revision 1.66
retrieving revision
diff -u -r1.66 -r1.66.2.1
--- sitemap.xmap        12 Feb 2003 02:30:39 -0000      1.66
+++ sitemap.xmap        28 Mar 2003 13:12:28 -0000
@@ -796,8 +796,8 @@
                <map:serialize type="fo2pdf" />
-            <map:match pattern="faq.pdf">
-               <map:generate type="file-nolabel" src="content/xdocs/faq.xml" />
+            <map:match pattern="**faq.pdf">
+              <map:generate type="file-nolabel" src="content/xdocs/{1}faq.xml" />
                <map:transform src="library/xslt/faq2document.xsl" label="content" />

In other words, if you have a binary Forrest distro, copy
context/sitemap.xmap to xml-security/doc/site/src/documentation/, and
apply that patch.

While you're hacking at Forrest sitemaps, you can also fix the other
build errors, relating to what I assume are Javadoc refs:

-> [broken page] Java/api/org/apache/xml/security/test/InteropTest.html
-> [broken page] Java/api/org/apache/xml/security/utils/resolver/ResourceResolver.html
-> [broken page] Java/api/org/apache/xml/security/signature/Reference.html

That can be done by changing this line in sitemap.xmap:

    <map:transform src="library/xslt/filterlinks.xsl" />


    <map:transform src="resources/stylesheets/filterlinks.xsl" />

Then copying Forrest's filterlinks.xsl (in the binary distro,
context/library/xslt/filterlinks.xsl) to
xml-security/doc/site/src/documentation/resources/stylesheets/, and

    <xsl:if test="not(contains(.,'apidocs')) and not(starts-with(., 'samples/')) 

to something like:

    <xsl:if test="not(contains(.,'Java/api')) 

filterlinks.xsl filters out links that the Cocoon crawler shouldn't
attempt to render.

> - In the site.xml file, we would like to define not only our external
>   references, but also contacts, mailinglists. I remember vaguely having
>   read something like that in the Forrest wish-list.
>   We now have external-refs like:
>   <kwouters label="Karel Wouters" href=""/>
> - As you see, I already defined my external-refs with an additional
>   label, such that we can use the something like this in the future:
>   <jump ext:sax/> instead of <jump ext:sax>SAX</jump>
>   When I have defined
>   <sax label="SAX" href=""/>
>   I guess I only need to change some XSLT files to do that, but we would
>   like to stick to the 'default' Forrest version.

We've had long discussions about how to decently emulate &entities; in
Forrest (using XInclude, etc).  Perhaps the simplest solution would be
to introduce a new XML element, <include id="sax"/>.  Then an XSLT
could simply look up /site/snippets/@id in site.xml, and pull in the
content defined there:

      <link href="">SAX</link>

Hmm.. needs more thinking over.

> All thing considered, I can say that we enjoyed porting our docs to Forrest
> and that we are happy with the result. It's a nice framework.
> Keep up the good work!



> Karel Wouters.

View raw message