For the developers interested, the code used is:
Code: Select all
response.setContentType("application/pdf");
response.setHeader("Content-Length", String.valueOf reportBytes.length));
response.setHeader("Content-disposition","inline; filename=ChemAlertIIReport.pdf");
Adobe Reader could not open 'pa027001.fdf' because it is either not a supported file type or because the file has been corrupted (for example, it was sent as an email attachment and wasn't correctly decoded).
Our immediate workaround was to change the above code to reflect the following:
Code: Select all
response.setHeader("Content-disposition","attachment; filename=ChemAlertIIReport.pdf");
StreamingContent.streamBytes(reportBytes, StreamingContentType.BINARY, response);
Then, just when I thought the workaround was going to alleviate the problem until the next product release, I had two clients report the same problem using Windows 2000 Server with Adobe Reader 5.1 / 6.0. Arrrrggghhh!!!
Has anyone seen this problem before (I've search Adobe & Microsoft support sites to no avail) and know how we could avoid this issue?
Thanks
Brad
Risk Management Technologies