migrating from a standalone application to a web application

[ma...@iworks.fr]

Hi

I use FOP in a standalone application in order to create PDF files.

Now the application users would like to use it in a multi-user (web) 
application.

I'd like to get a few advices on how to migrate my application.
I've read the "embedding" and "servlet" pages on FOP's site carefully.

I intend to pool renderers and drivers. I wonder if there is a Jakarta 
package that would be helpful.

When I run the application on my Windows 2000 computer, the JVM uses a lot 
of CPU while rendering (almost 100 %). Il wonder if this would be improved 
if I use the server option of Sun's JVM.

I use :
- FOP 0.20.5
- Tomcat 4.1.18
- Sun's JVM 1.4.0_03 on windows 2000

Thanks for your advices,

Mathieu

 

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org

Re: migrating from a standalone application to a web application

[Jeremias Maerki <de...@greenmail.ch>]

On 19.02.2004 11:31:52 mathieu.fretiere wrote:
> I use FOP in a standalone application in order to create PDF files.
> 
> Now the application users would like to use it in a multi-user (web) 
> application.
> 
> I'd like to get a few advices on how to migrate my application.
> I've read the "embedding" and "servlet" pages on FOP's site carefully.
> 
> I intend to pool renderers and drivers. I wonder if there is a Jakarta 
> package that would be helpful.

I don't think that pooling renderers and drivers will bring much more
than trouble. The biggest number of objects created and destroyed are in
the FO tree and the area tree which have to be built in every processing
run anyway. I'd say: don't bother pooling.

> When I run the application on my Windows 2000 computer, the JVM uses a lot 
> of CPU while rendering (almost 100 %). Il wonder if this would be improved 
> if I use the server option of Sun's JVM.

Maybe, but I don't think so. FOP is rather CPU-intensive and there's not
much you can do about it. Try to simplify and optimize your stylesheets,
think about using XSLTC (See Xalan) or a different XSLT processor
altogether. You may have to experiment a bit.


Jeremias Maerki


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-user-unsubscribe@xml.apache.org
For additional commands, e-mail: fop-user-help@xml.apache.org