Joerg,
What did you mean by this
--
FOP is not generally slow but under certain circumstances.
Try to use the FOP command line application to render your PDF and
watch the output. If you get lots of overflows, indicated by a ""
or an "INFO: " line, you'll have to fiddle with column widths and
It happened to me using IE to Tomcat on the local machine using
'localhost'. I switched to using the real network interface and it
fixed itself.
Joe
Alex Amies wrote:
I have a problem with a servlet, which serves up pdf documents,
invoking the servlet twice for every time I request the
url
Alex McLintock wrote:
I've seen the content size problem (which you have correctly solved in your code)
but now I have a problem with a particular build of IE. Basically the PDF doesn't
appear -
in fact neither does acrobat reader
The problem occurs on the IE version 5.50.4522.1800 and not
When FOP is a production ready library, I wont care for any FOP logging.
Logging in FOP now is only for debugging as far as I'm concerned. There
is no need for integration into other logging systems.
Think about how you use other libraries.
Joe
2 more cents...
I am using FOP in production.
We have a major problem with performance, but have a working app with
bad performance beats no app. Generating 200 page reports uses GBs of
memory and 3 to 10 minutes of a single CPU on a quad 500 PIII. Our
document is a single table. The
