cdeal

Thought I was losing my mind, I couldn't remember EXACTLY what it was, just the general idea. I finally found it. JRXmlConstants is a utility class that builds Map objects to be used (I'm guessing) by the XML parsing process. In v3.5.2 these returned the Map directly. In 3.5.3, this code was changed to return Collections.unmodifiableMap wrappers. I found that problem while debugging and shortly after I found it it, 3.5.3 was released and fixed the problem. The problem wasn't any single method, but all of them were suspect and in our case it was more than one attribute that was affected. No problems since moving to 3.5.3.

The problem was fixed in jasperreports 3.5.3. The problem is that the Map objects that get returned from the methods (something like getAlignmentMap) were not safe in 3.5.2. In 3.5.3 the methods return unmodifiable maps which correct the problem.

I would have to agree. It also seems that reporters have specifically mentioned iReports 3.5.2. Are there any other iReports versions being affected? It seems more likely that something got introduced in the iReports/JasperReports code that is inadvertently damaging the Map of enum values. Are the Maps "edit-proof", meaning do they have protections against being modified after being initialized?

This also happens with this version of the JVM, so I guess I'll have to try a newer release. java version "1.5.0_14" Java 2 Runtime Environment, Standard Edition (build 1.5.0_14-b03) Java HotSpot Client VM (build 1.5.0_14-b03, mixed mode)

I have been experiencing this problem as well as the problem where attributes get saved as "null" in v 3.5.2. java version "1.5.0_14" Java 2 Runtime Environment, Standard Edition (build 1.5.0_14-b03) Java HotSpot Client VM (build 1.5.0_14-b03, mixed mode)

Look up information on the "exclude.key" property. Code:<property name="net.sf.jasperreports.export.xls.exclude.key.{keyvalue}" />

Can you offer any more details on this solution? A number of JR versions have been released since this post. Is there a workaround for this subreport problem? Post Edited by cdeal at 08/12/2009 17:27

I couldn't believe that it didn't work as I expected, so I went back over the code (not that I hadn't been trying off and on for the past couple of days now...). The dev who originally wrote the report had a PrintWhenExpression on the field that was turning it off. So, this one is COMPLETELY operator error. Sorry about that. Chuck

Many of our reports show the report criteria that was used to generate/customize the report. However, most of the time, this information is an ID instead of useful text. We normally show a field from the resultset in the header to represent the parameters used by the report, but when the report contains no data, those fields aren't available either; therefore, they show up blank in the output. We thought that we could correct this problem be sending in the parameter text along with the parameter id (two separate parms) but the report will not show the parmeters when there is no data either. The only way that I have found, is to wrap the parameter with a variable that has it's initial value set to the param value. This seems like a lot of extra effort. We are using JR 2.0.2 and I believe that it happened with JR 1.2.4. We already use "All Sections No Detail". Why doesn't the report display fields that contain PARAMETER values when there is no data when it WILL display a VARIABLE in the same case? Is there some setting? Does it make sense to do this? Is my work around the only way to accomplish this? Chuck

Many of our reports show the report criteria that was used to generate/customize the report. However, most of the time, this information is an ID instead of useful text. We normally show a field from the resultset in the header to represent the parameters used by the report, but when the report contains no data, those fields aren't available either; therefore, they show up blank in the output. We thought that we could correct this problem be sending in the parameter text along with the parameter id (two separate parms) but the report will not show the parmeters when there is no data either. The only way that I have found, is to wrap the parameter with a variable that has it's initial value set to the param value. This seems like a lot of extra effort. We are using JR 2.0.2 and I believe that it happened with JR 1.2.4. We already use "All Sections No Detail". Why doesn't the report display fields that contain PARAMETER values when there is no data when it WILL display a VARIABLE in the same case? Is there some setting? Does it make sense to do this? Is my work around the only way to accomplish this? Chuck