Hi everyone,

I have been using FOP for a couple of years, and while it worked for me, my documents would take a long time to render and I would wonder if my request actually went through. Plus, my users would get aggravated. Anyway, I did some of the tricks one can do and rewrote my program to "check" if it was done.

Anyway to make a long story short, I wrote a filter that will provide a status page to the user WITHOUT having to write or modify a line of code. I can put the servlet filter in front of any request that runs long without modifying anything. So you can put it in front of struts, in front of fop servlet, a jsp, etc...

I "configured" a specific webapp of FOP that uses this filter and you can run it. Notice that I said "configured" since I did not actually have to write this, I just configured FOPServlet(came with distribution) and web.xml to show you that I did not have to write or modify code.

One of the features that it has is to calculate the average time for the request and use that to predicate the status bar.
All the code is in CVS, and there is a snap shot of it. It's LGPL.


Just wanted to share.
http://rhoderunner.com/longrequest/

BTW, for now it's on a test server that has an automated build system (pull from cvs, deploy to tomcat) so it may not be up 100% of the time. If at first you don't succeed, try try again!








I




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to