You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by El...@aib.ie on 2008/07/28 19:12:11 UTC

[Trinidad] fileDownloadActionListener duplicate events

Hi,
 
I'm writing an application using Trinidad (1.0.8) and JasperReports (3.0.0). I have two jsps that with two separate backing beans generating the pdf reports. I'm using the tr:fileDownloadActionListener tag to manage the file downloads to the browser. The issue I'm having is that on one of the pages generates the reports with no problems. On the second page, the report initially gets generated successfully, but on subsequent events on the same page (e.g. valueChangeListener events) the report is regenerated and a download dialog box appears. This does not happen on the other page. I've tried calling the renderResponse method at the end of each report generation and event methods, and this has no effect. I've also tried using a response stream to send the report back to the client, and the same issue occurrs.
 
Has anyone had any similar problems?
 
Many thanks,
 
Elaine

Re: [Trinidad] fileDownloadActionListener duplicate events

Posted by Matthias Wessendorf <ma...@apache.org>.
Hi,

what is the difference between the two pages?

-M

On Mon, Jul 28, 2008 at 7:12 PM,  <El...@aib.ie> wrote:
> Hi,
>
> I'm writing an application using Trinidad (1.0.8) and JasperReports (3.0.0).
> I have two jsps that with two separate backing beans generating the pdf
> reports. I'm using the tr:fileDownloadActionListener tag to manage the file
> downloads to the browser. The issue I'm having is that on one of the pages
> generates the reports with no problems. On the second page, the report
> initially gets generated successfully, but on subsequent events on the same
> page (e.g. valueChangeListener events) the report is regenerated and
> a download dialog box appears. This does not happen on the other page. I've
> tried calling the renderResponse method at the end of each report generation
> and event methods, and this has no effect. I've also tried using a response
> stream to send the report back to the client, and the same issue occurrs.
>
> Has anyone had any similar problems?
>
> Many thanks,
>
> Elaine
>



-- 
Matthias Wessendorf

further stuff:
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
mail: matzew-at-apache-dot-org