Mailing-List: contact issues-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Date: Sun, 4 Mar 2012 16:47:58 +0000 (UTC)
From: "Bilgin Ibryam (Commented) (JIRA)" <jira@apache.org>
To: issues@camel.apache.org
Message-ID: 
 <753732569.19925.1330879679006.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CAMEL-3551) camel-fop component
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CAMEL-3551?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1322=
1931#comment-13221931 ]=20

Bilgin Ibryam commented on CAMEL-3551:
--------------------------------------

I'm working on committing my old patch here, but I'm not sure how karaf/sev=
icemix works.=20
Looking at SMX4-963, I see there are 3 boundles: batik, for and xmlgraphioc=
s. Do I need to add all of them camel platform features or only fop bunlde?
               =20
> camel-fop component
> -------------------
>
>                 Key: CAMEL-3551
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3551
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Jean-Baptiste Onofr=C3=A9
>            Assignee: Bilgin Ibryam
>             Fix For: Future
>
>         Attachments: camel-fop.diff
>
>
> A new Camel FOP component could be helpful to turn Camel into a kind of p=
rintout and report generation system.
> A typical use case could be something like:
> from("amq:my.document.queue")
>   .to("xslt:mystylesheet.xsl")
>   .to("fop:pdf?some.extra.options.here")
>   .to("file:outputdirectory")
>   .to("printer:some.printer");

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs: https://issues.apache.org/jira/secure/ContactAdministrators!default.jsp=
a
For more information on JIRA, see: http://www.atlassian.com/software/jira