Hello Bilgin!
That's really great. I think this is a good improvement for reporting
requirements, ...
At present we are focusing to stabilize Camel 2.9.0 (Camel 2.9.0-RC1 will
be available in the next week) to be able to release it in a few weeks.
After Camel 2.9.0 is out, I'm sure one of the commiter will pick up the
JIRA and work on it.
Best,
Christian
On Fri, Nov 4, 2011 at 1:20 PM, Bilgin Ibryam <bibr...@gmail.com> wrote:
> Hi all,
>
> I've created a camel-fop component that uses Apache FOP project to
> render Camel messages into different outputs like PDF, PostScript,
> PCL, AFP, RTF, PNG etc [1].
>
> The component has only a producer, which expects in the message body
> xml in XSL-FO format that can be generated from XML data and XSLT
> template, or using freemarker or velocity templates. Then transforms
> it to the output format specified in the endpoint URL or message
> header.
>
> Also it is possible to set metadata per document (like producer,
> author, creation data, resolution) or encrypt the documents with
> password.
>
> Additionally it has options to override the default fop config file by
> specifying a new userConfig location [2] in the endpoint URL.
>
> Here is an example of creating PDFs from xml data and xslt template:
>
> .from("file:source/data/xml")
> .to("xslt:xslt/template.xsl")
> .to("fop:application/pdf")
> .to("file:target/data");
>
> I think this would enhance the reporting capabilities of Came a lot. WDYT?
> The patch is attached to the existing issue
> https://issues.apache.org/jira/browse/CAMEL-3551
>
> [1]http://xmlgraphics.apache.org/fop/0.95/output.html
> [2]http://xmlgraphics.apache.org/fop/1.0/embedding.html#config-internal
>
>
> Cheers,
>
> --
> Bilgin Ibryam
> b.ibr...@sourcesense.com
> Sourcesense - making sense of Open Source: http://www.sourcesense.com
>
