This does sound like a compat issue. It seems like one down-side of iReport
is its sensitivity to versions between the authoring tool and the runtime.

We currently ship with version 4.0.1 of the jasper runtime.

If we regularly update this jar, we will break previously authored reports.
If we do not regularly update, we will miss bug fixes, new features, etc.

To work in an updated runtime, an existing report must be recompiled with
the authoring tool that matches the runtime version. As such, I would
recommend that we update the reporting runtime infrequently. However, I am
open to suggestions on this. At this point we are a year behind, and AFAIK,
there are relatively few reports that have been authored. As such, we should
probably update the jasper runtime soon. Looks like 4.5 was a big release
for them, but did not add functionality we need so much. However, previous
releases (4.1.1 and 4.1.2) fixed lots of bugs, and we might as well go with
their latest and greatest.

For now (i.e., until we resolve to update the jasper lib we integrate), you
need to use the 4.0.1 version of iReport. You can find older versions at:
http://sourceforge.net/projects/ireport/files/iReport/
http://sourceforge.net/projects/ireport/files/iReport/.

Patrick

From: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] On Behalf Of Chris Hoffman
Sent: Tuesday, February 21, 2012 2:34 PM
To: CollectionSpace Talk List
Subject: [Talk] iReport compatibility issue?

Hi all,
I'm eager to get a report working on CollectionSpace!  After the usual back
and forth, I finally have a report installed on one of our servers, but when
I try to run it, I get an error, which in cspace-services.log starts out
with this:

2012-02-21 14:00:30,272 DEBUG [http-8180-7]
[org.collectionspace.services.report.ReportResource:387]
org.collectionspace.services.report.ReportResource
java.lang.NullPointerException
at java.lang.Class.isAssignableFrom(Native Method)
at
net.sf.jasperreports.engine.fill.JRFillTextField.getFormat(JRFillTextField.j
ava:706)
at
net.sf.jasperreports.engine.fill.JRFillTextField.evaluateText(JRFillTextFiel
d.java:394)

Googling for some of this, I found discussions about iReport version
compatibility issues, e.g.,

http://stackoverflow.com/questions/7776968/exception-in-jasperprint-in-jaspe
rreport

http://www.fishbowlinventory.com/forums/viewtopic.php?f=14
http://www.fishbowlinventory.com/forums/viewtopic.php?f=14&t=2814&p=12056
&t=2814&p=12056

This reminded me that I just updated my version of iReport to 4.5.  Is it
possible that my reports are not compatible with the version of some iReport
jar file in the CSpace 2.0 release that I'm working on?

Thanks,
Chris

Go figure. The runtime dependency says 4.0.1. I have a vague recollection
that their maven repository was out of date, and so we made 4.0.1 the
version.

Thanks for checking the docs. I do have 4.0.2 client installed (just checked
my client), and that is how I authored and tested the reports I did last
year.

Compiling with a down-version client is likely to cause problems that going
the other direction generally should not.

Sorry for the hassle -

Patrick

From: Chris Hoffman [mailto:chris.hoffman@berkeley.edu]
Sent: Tuesday, February 21, 2012 4:22 PM
To: Patrick Schmitz
Cc: 'CollectionSpace Talk List'
Subject: Re: [Talk] iReport compatibility issue?

By the way, according to

http://wiki.collectionspace.org/display/DOC/Notes+on+report+authoring+with+i
Report
CSpace is actually using iReport 4.0.2 (instead of 4.0.1).  I tried using
4.0.1 but had some problems (though I might have had some 4.5 stuff still in
the report file I recompiled in 4.0.1).
Chris

On Feb 21, 2012, at 3:00 PM, Patrick Schmitz wrote:

This does sound like a compat issue. It seems like one down-side of iReport
is its sensitivity to versions between the authoring tool and the runtime.

We currently ship with version 4.0.1 of the jasper runtime.

If we regularly update this jar, we will break previously authored reports.
If we do not regularly update, we will miss bug fixes, new features, etc.

To work in an updated runtime, an existing report must be recompiled with
the authoring tool that matches the runtime version. As such, I would
recommend that we update the reporting runtime infrequently. However, I am
open to suggestions on this. At this point we are a year behind, and AFAIK,
there are relatively few reports that have been authored. As such, we should
probably update the jasper runtime soon. Looks like 4.5 was a big release
for them, but did not add functionality we need so much. However, previous
releases (4.1.1 and 4.1.2) fixed lots of bugs, and we might as well go with
their latest and greatest.

For now (i.e., until we resolve to update the jasper lib we integrate), you
need to use the 4.0.1 version of iReport. You can find older versions at:
http://sourceforge.net/projects/ireport/files/iReport/
http://sourceforge.net/projects/ireport/files/iReport/.

Patrick

From: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] On Behalf Of Chris Hoffman
Sent: Tuesday, February 21, 2012 2:34 PM
To: CollectionSpace Talk List
Subject: [Talk] iReport compatibility issue?

Hi all,
I'm eager to get a report working on CollectionSpace!  After the usual back
and forth, I finally have a report installed on one of our servers, but when
I try to run it, I get an error, which in cspace-services.log starts out
with this:

2012-02-21 14:00:30,272 DEBUG [http-8180-7]
[org.collectionspace.services.report.ReportResource:387]
org.collectionspace.services.report.ReportResource
java.lang.NullPointerException
at java.lang.Class.isAssignableFrom(Native Method)
at
net.sf.jasperreports.engine.fill.JRFillTextField.getFormat(JRFillTextField.j
ava:706)
at
net.sf.jasperreports.engine.fill.JRFillTextField.evaluateText(JRFillTextFiel
d.java:394)

Googling for some of this, I found discussions about iReport version
compatibility issues, e.g.,

http://stackoverflow.com/questions/7776968/exception-in-jasperprint-in-jaspe
rreport

http://www.fishbowlinventory.com/forums/viewtopic.php?f=14
http://www.fishbowlinventory.com/forums/viewtopic.php?f=14&t=2814&p=12056
&t=2814&p=12056

This reminded me that I just updated my version of iReport to 4.5.  Is it
possible that my reports are not compatible with the version of some iReport
jar file in the CSpace 2.0 release that I'm working on?

Thanks,
Chris