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
I agree with Markus.
FOP needs so much JARs and rendering PDF take so much ressources that I
think it's better to do the transformations server side and then send the
result to the client. That is my opinion about using FOP clientside with
an applet (for web app, I think the servlet approach
I use FOP on the client side. The application (not applet) offers
templates for different kinds of documents e.g. invitations,
advertisements etc. The user can enter text and choose from
an image list (remote db and local files) and the app
produces a pdf. In my case it was better to use fop on
Hello David
We are using FOP in several productive applications in a insurance
environment.
Mit freundlichen Grüssen
Helmut Gehrer
Visana Services AG
E-Mail: [EMAIL PROTECTED]
URL: www.visana.ch
-Ursprüngliche Nachricht-
Von: Holk, David A [mailto:[EMAIL PROTECTED]
Gesendet:
Hi David,
We are just starting to use FOP for Printing and PDF Streaming issues in
A Data Warehouse application.
Works good, no big stones in our way, yet :-)
Greetings
Normen
-Ursprüngliche Nachricht-
Von: Holk, David A [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 10. März 2003
