Uh, I forgot, PdfDataSource is final, so option B is not even an option
now ;)
Matej Knopp wrote:
Btw, there's a problem with current implementation. After the report is
done, you can't generated another report (e.g. clicking twice on the
same link). Because datasource is the same and it's at
Btw, there's a problem with current implementation. After the report is
done, you can't generated another report (e.g. clicking twice on the
same link). Because datasource is the same and it's at the end. So all
further calls to datasource.next() will result in false.
The solution now is eithe
Checked it out, I really like it. Mine was just a quick hack ;)
-Matej
Eelco Hillenius wrote:
Thanks. Much better now. I implemented a couple of small changes on
top of it, please check out whether you agree (find the patch
attached).
Eelco
Matej Knopp wrote:
Hi.
There's a slight perform
Thanks. Much better now. I implemented a couple of small changes on
top of it, please check out whether you agree (find the patch
attached).
Eelco
>
> Matej Knopp wrote:
> > Hi.
> >
> > There's a slight performace problem with JRResource, that it creates
> > JasperReport in it's constructor. I've
Okay, once more, without antivirus message attached to java file and one
unnecessary try/catch block :)
Matej Knopp wrote:
Hi.
There's a slight performace problem with JRResource, that it creates
JasperReport in it's constructor. I've 10 resource links on one page so
it means that 10 Jasper
Hi.
There's a slight performace problem with JRResource, that it creates
JasperReport in it's constructor. I've 10 resource links on one page so
it means that 10 JasperReports will be initialized everytime page is
created, even if none of them gets clicked. The performance penalty is
not sma
