Hi, You have to consider the additional JARs used by FOP (Xalan, Avalon, ...). IMHO you get somewhat around 5 MB of JARs. It will take a long time for your users to download so much stuff (at least the first time they use the applet). This was the reason for us to have FOP on the server and send PDF from there to the client.
Markus $> -----Ursprüngliche Nachricht----- $> Von: Van Camp, Kenneth (Exchange) [mailto:[EMAIL PROTECTED] $> Gesendet: Mittwoch, 12. März 2003 14:56 $> An: '[EMAIL PROTECTED]' $> Betreff: RE: FOP in production app $> $> $> I saw a number of posted responses to David's query but it $> seems like most $> respondents are using FOP on the server side. Is there much $> experience in $> using FOP on the client side, say inside of an applet? I am $> interested in $> streaming XSLT to the user's browser and having an applet $> transform it into $> a PDF, then invoke Acrobat reader to render it on the desktop. $> $> Is this a common application? It is related to this thread $> in that I am $> concerned about production support in such an environment. $> $> Is there a better way? Thanks. $> $> Ken Van Camp <[EMAIL PROTECTED]> $> $> -----Original Message----- $> From: Holk, David A [mailto:[EMAIL PROTECTED] $> Sent: Monday, March 10, 2003 12:37 PM $> To: '[EMAIL PROTECTED]' $> Subject: FOP in production app $> $> $> Is anyone using FOP in a production app? $> $> Should I expect a commercial product like XEP or $> XSLFormatter to be more $> robust in a production application? $> $> Any experiences/comments appreciated. $> $> David Holk $> $> $> LEGAL NOTICE $> Unless expressly stated otherwise, this message is $> confidential and may be $> privileged. It is intended for the addressee(s) only. Access $> to this E-mail $> by anyone else is unauthorized. If you are not an addressee, $> any disclosure $> or copying of the contents of this E-mail or any action $> taken (or not taken) $> in reliance on it is unauthorized and may be unlawful. If $> you are not an $> addressee, please inform the sender immediately. $> $> --------------------------------------------------------------------- $> To unsubscribe, e-mail: [EMAIL PROTECTED] $> For additional commands, e-mail: [EMAIL PROTECTED] $> $> $> ************************************************************* $> ********** $> Bear Stearns is not responsible for any recommendation, $> solicitation, $> offer or agreement or any information about any transaction, $> customer $> account or account activity contained in this communication. $> ************************************************************* $> ********** $> $> $> --------------------------------------------------------------------- $> To unsubscribe, e-mail: [EMAIL PROTECTED] $> For additional commands, e-mail: [EMAIL PROTECTED] $> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
