I found a little bug in wicket-contrib-jasperreport code using a recent
JasperReports version (2.0.2 in my application, but the problem is there
also with previous releases) with Wicket 1.3.
The problem is in class JRResource not being Serializable and is determined
by the call to JasperFillManager.fillReport(report, params, dataSource)
that change the reportParameters (it's an HashMap) variable adding not
serializable objects to it.
A simple solution is replacing the code in getReportParameters() avoiding
to return directly the variable:
public Map getReportParameters()
{
//modified for jasperreport 2.0.2 serialization problem
return new HashMap(reportParameters);
}
How would like to report this as a bug on Wicket Stuff Jira but there I can'
found the wicket-contrib-jasperreport project.
Any other way?
Luciano
--
View this message in context:
http://www.nabble.com/How-to-report-a-bug-on-wicket-contrib-jasperreport--tp14258881p14258881.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
