forrest-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andy J <>
Subject Re: Help w/transforming an aggregated doc
Date Tue, 04 Jan 2005 17:05:53 GMT
Alas, I tried that, too.  My tabs.xml actually refers to projects.html
which I figured the Forrest machinery would then implicitly make a
call which would match projects.xml (the aggregated document) but
would still need to be returned as HTML.  In any case, I tried both
ways.  Here's the relevant snippet from site.xml:
  <projects label="Projects" description="Project Information" tab="projects" />

And from tabs.xml:
  <tab id="projects" label="Projects" dir="projects/"

I added a log transformer which gets the content.  And the PDF gets
the content but dagblasted it's not getting into the HTML!  I just
tried the docs2document.xsl and have tried others.  Am I right in that
the aggregate will spit out a very basic composite of my two documents
and then pipe it to the XSL?  Any other ideas?

- Andy

On Tue, 04 Jan 2005 16:47:40 +0000, Ross Gardler <> wrote:
> Andy J wrote:
> > This is killing me!  I feel like I'm moving forward but still can't
> > get this to work.  I'm trying to aggregate two documents.  One is the
> > header element, the other the body and the aggregate element is
> > document.  I thought I was supposed to be trying to generate an Apache
> > DTD v2.0 document.  The PDF is generated and _has content_, but the
> > HTML is blank which makes me suspect that the problem has to do with
> > the document type and things being dropped in the xsl transformation.
> > I tried setting up an action (copied from forrest.xmap) but still the
> > HTML comes up empty (other than the skinning).
> ...
> > ANY guidance would be GREATLY appreciated!  Thanks!
> >
> ...
> >       <map:match pattern="**projects/projects.xml">
> ...
> >         <map:serialize type="html"/>
> You are requesting the XML document, but serialising as HTML. Change the
> serialiser to XML and test again.
> --
> No virus found in this outgoing message.
> Checked by AVG Anti-Virus.
> Version: 7.0.300 / Virus Database: 265.6.8 - Release Date: 03/01/2005

View raw message