Hello Katharina,
the problem is, that the xinclude command does not access the second
pipeline, but searches for a file on the hard disk. You need to prefix
the href value with the cocoon:/ pseudo protocol to get back to the sitemap:
<xi:include>
<xsl:attribute
name="href"><xsl:text>bsplt_pdf_stockwerk</xsl:text></xsl:attribute>
</xi:include>
must be changed to
<xi:include>
<xsl:attribute
name="href"><xsl:text>cocoon:/bsplt_pdf_stockwerk</xsl:text></xsl:attribute>
</xi:include>
or in shortform:
<xi:include href="cocoon:/bsplt_pdf_stockwerk"/>
Regards
Jörg
On 01.05.2006 09:26, Katharina Kreis wrote:
Hi!
I'm trying to integrate a svg graphic into a pdf doc using xinclude.
I have one matcher which should create a pdf file using the fo2pdf
serializer. I produce the 'fo' content for the pdf with a xslt file
named 'pdftest.xsl'. In this file, I have a xinclude inside, which
references to another matcher called 'bsplt_pdf_stockwerk'. This matcher
creates a large svg file (here I have only a sample file). Both matchers
are working without the xinclude command. If I have the xinclude command
inside, I get directly after the xinclude transformer the error message:
A xml file must have a root element. But both files have! Can anybody
tell me what is wrong here?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]