forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ron Blaschke (JIRA)" <>
Subject [jira] Commented: (FOR-546) Sitemap reference doc should be updated to reflect plugin architecture
Date Sat, 18 Jun 2005 13:52:18 GMT
    [ ] 

Ron Blaschke commented on FOR-546:

Sorry, should have been more specific.  I am using the docbook stylesheets (,
and my own pipeline.

      <map:match pattern="design.pdf">
        <map:generate src="{project:content.xdocs}design.xml"/>
        <map:transform src="resources/stylesheets/docbook/fo/docbook.xsl"/>
        <map:serialize type="fo2pdf"/>

I know, this is my problem and not forrest's, but adding the fo2pdf serializer is something
that people need to be aware of when upgrading from 0.6 to 0.7.  But I guess
a sufficient hint...

> Sitemap reference doc should be updated to reflect plugin architecture
> ----------------------------------------------------------------------
>          Key: FOR-546
>          URL:
>      Project: Forrest
>         Type: Improvement
>   Components: Documentation and website
>     Versions: 0.7-dev
>     Reporter: Ron Blaschke

> The example at uses a fo2pdf
serializer.  This probaly worked in versions < 0.7, because the PDF output feature was
in the core, and the serializer was very likely declared there.
> With version 0.7, PDF output is moved to a plugin, the fo2pdf serializer seems to be
no longer there.  The serializer should probably be added to the example, for completeness.
>   <map:components>
>     <map:serializers>
>       <map:serializer name="fo2pdf"
>                       src="org.apache.cocoon.serialization.FOPSerializer"
>                       mime-type="application/pdf"/>
>     </map:serializers>
>   </map:components>
> I found out about this because my sitemap uses the fo2pdf too (docbook to PDF), and had
to add the serializer.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message