The samplewebapp uses a different version of JasperReports (1.2.7) from JasperServer (1.2.0) which uses 1.3.0. This causes problem for some report when the deserialisation of the jrprint object discovers version number differences.
In general it might be a better architecture (if that is possible) to receive the xls, pdf or html from the server rather than the jrprint object. If that is not possible at least the version numbers of the libraries in the server and the sample app have to be the same.
Issue exists with 1.2.0.
Manfred Moser: 03/19/2007 1:03 PM PDT
the stack trace is in the attached file.
the significant bit is probably
java.io.InvalidClassException: net.sf.jasperreports.engine.util.JRTextAttribute; local class incompatible: stream classdesc serialVersionUID =
1985145853444784481, local class serialVersionUID = -614521145983454755 at java.io.ObjectStreamClass.
Attachment: stacktrace.log (19.78 KB)
Added an attachment.
Teodor Danciu: 03/19/2007 2:47 AM PDT
Can you provide us with the stack trace of the exception you get?