You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Luciano Montebove (JIRA)" <ji...@apache.org> on 2007/12/11 11:14:43 UTC
[jira] Created: (WICKET-1217) wicket-contrib-jasperreport
JRResource serialization problem
wicket-contrib-jasperreport JRResource serialization problem
------------------------------------------------------------
Key: WICKET-1217
URL: https://issues.apache.org/jira/browse/WICKET-1217
Project: Wicket
Issue Type: Bug
Affects Versions: 1.3.0-rc1
Reporter: Luciano Montebove
Priority: Minor
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 there is a bug in class JRResource that make it not serializable generating errors from the Wicket 1.3 serialization ckecks. It is determined by the call to JasperFillManager.fillReport(report, params, dataSource) that changes the reportParameters (it's an HashMap) variable adding not serializable objects to it.
A simple solution is replacing the code in getReportParameters() of JRResource avoiding to return directly the variable:
public Map getReportParameters()
{
//modified for jasperreport 2.0.2 serialization problem
return new HashMap(reportParameters);
}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-1217) wicket-contrib-jasperreport
JRResource serialization problem
Posted by "Luciano Montebove (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luciano Montebove resolved WICKET-1217.
---------------------------------------
Resolution: Fixed
Fixed in revision 3360 of wicket-contrib-jasperreports.
> wicket-contrib-jasperreport JRResource serialization problem
> ------------------------------------------------------------
>
> Key: WICKET-1217
> URL: https://issues.apache.org/jira/browse/WICKET-1217
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.3.0-rc1
> Reporter: Luciano Montebove
> Priority: Minor
>
> 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 there is a bug in class JRResource that make it not serializable generating errors from the Wicket 1.3 serialization ckecks. It is determined by the call to JasperFillManager.fillReport(report, params, dataSource) that changes the reportParameters (it's an HashMap) variable adding not serializable objects to it.
> A simple solution is replacing the code in getReportParameters() of JRResource avoiding to return directly the variable:
> public Map getReportParameters()
> {
> //modified for jasperreport 2.0.2 serialization problem
> return new HashMap(reportParameters);
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (WICKET-1217) wicket-contrib-jasperreport JRResource
serialization problem
Posted by "Luciano Montebove (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luciano Montebove closed WICKET-1217.
-------------------------------------
> wicket-contrib-jasperreport JRResource serialization problem
> ------------------------------------------------------------
>
> Key: WICKET-1217
> URL: https://issues.apache.org/jira/browse/WICKET-1217
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 1.3.0-rc1
> Reporter: Luciano Montebove
> Priority: Minor
>
> 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 there is a bug in class JRResource that make it not serializable generating errors from the Wicket 1.3 serialization ckecks. It is determined by the call to JasperFillManager.fillReport(report, params, dataSource) that changes the reportParameters (it's an HashMap) variable adding not serializable objects to it.
> A simple solution is replacing the code in getReportParameters() of JRResource avoiding to return directly the variable:
> public Map getReportParameters()
> {
> //modified for jasperreport 2.0.2 serialization problem
> return new HashMap(reportParameters);
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.