DJ aspirant, Engineering undergraduate, Tokusatsus addicted, fond of English language and Asia's, Buddhist, blogger, etc. I'll need to insert all these attributes in a Java class and manage to create methods for handling my overwhelming life
JSF is not an all-or-nothing architecture. A JSF app can also contain servlets, traditional JSPs, and even Struts code.
The power of JSF is that allows you to manage HTML content (especially form content) easily. It does that by assuming total control over the HttpResponse and its output stream, however, and you inject your own low-level efforts at your peril.
It's a lot safer, cleaner, and simpler to provide the ZIP download from a servlet that to try and force JSF to do it.
There's a related thread on this forum where I've discussed similar issues.
An IDE is no substitute for an Intelligent Developer.
Joined: Mar 30, 2005
Marcos Silvestri wrote:It's been a long time now, but it does not hurt asking...
Have this be resolved?
Jordan, if you're still around and remember how to solve this, I'd be glad to have your thoughts.
The best solution that worked for me is to stop adding the response content behaviour manipulations in JSF.
Try adding response.complete and just do a flush before closing the streams. No need to use ZipOutput streams. Use buffer streams only if you are planning on sending huge data(more than 2 MB/4 MB approx)