JS 3.7 CE - Report Error 'keepTogether'

[manshack_one]

I'm using keepTogether in iReport to keep a group from splitting on the first page.  It works perfectly and I get exactly what I need but the following error occurs if I try and run it on JS.  It compiles just fine in iReport 3.7.

java.lang.Exception: 1 - org.xml.sax.SAXParseException: cvc-complex-type.3.2.2: Attribute 'keepTogether' is not allowed to appear in element 'group'. 
    at com.jaspersoft.ireport.jasperserver.ws.WSClient.runReport(WSClient.java:403) 
    at com.jaspersoft.ireport.jasperserver.ws.WSClient.runReport(WSClient.java:320) 
    at com.jaspersoft.ireport.jasperserver.ReportRunner.run(ReportRunner.java:70) 
    at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:572) 
    at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:997) 

[mdahlman]

It looks like a JasperReports version mismatch between iReport and JasperServer.

Update your JasperServer to use the same version of JR that iReport is using and the problem should go away.

Regards,
Matt

[manshack_one]

How can they be different versions?  I'm using iReport 3.7 and JS 3.7.  Here's a jdbc info report that might help. 

$P{REPORT_CONNECTION}.getMetaData().getDriverVersion()

http://10.16.200.51:8081/jasperserver/reportimage?jrprint=27833405_1267626545716&image=px

http://10.16.200.51:8081/jasperserver/reportimage?jrprint=27833405_1267626545716&image=px

http://10.16.200.51:8081/jasperserver/reportimage?jrprint=27833405_1267626545716&image=px

mysql-connector-java-5.1.5 ( Revision: ${svn.Revision} )

http://10.16.200.51:8081/jasperserver/reportimage?jrprint=27833405_1267626545716&image=px

http://10.16.200.51:8081/jasperserver/reportimage?jrprint=27833405_1267626545716&image=px

http://10.16.200.51:8081/jasperserver/reportimage?jrprint=27833405_1267626545716&image=px

net.sf.jasperreports.engine.JasperReport.class.getPackage().

http://10.16.200.51:8081/jasperserver/reportimage?jrprint=27833405_1267626545716&image=px

http://10.16.200.51:8081/jasperserver/reportimage?jrprint=27833405_1267626545716&image=px

3.6.2-SNAPSHOT

http://10.16.200.51:8081/jasperserver/reportimage?jrprint=27833405_1267626545716&image=px

http://10.16.200.51:8081/jasperserver/reportimage?jrprint=27833405_1267626545716&image=px

http://10.16.200.51:8081/jasperserver/reportimage?jrprint=27833405_1267626545716&image=px

getClass().getResource("/com/mysql/jdbc/Driver.class").toString()

http://10.16.200.51:8081/jasperserver/reportimage?jrprint=27833405_1267626545716&image=px

http://10.16.200.51:8081/jasperserver/reportimage?jrprint=27833405_1267626545716&image=px

http://10.16.200.51:8081/jasperserver/reportimage?jrprint=27833405_1267626545716&image=px

jar:file:/opt/jasperserver-ce-3.7.0/apache-tomcat/webapps/jasperserver/WEB- INF/lib/mysql-connector-java-5.1.5.jar!/com/mysql/jdbc/Driver.class

[manshack_one]

Is it the 3.6.2 Snapshot that's the issue? Was that the JR version for JS 3.7 CE? If that has to be upgraded I'll need some help getting the jars in the right place on the server. I noticed when I run the report locally in iReport it's coming back as 3.7.

[manshack_one]

I'm realizing now that I installed JS 3.7 CE RC. I guess it didn't bundle in JR 3.7 until the general release. Well, now I'll have to post on how to get this upgraded without losing all my reports, datasources, input controls, etc.

[mdahlman]

If you have trouble with the upgrade, please start a new thread (as you already suggested).

The process should be easy:

• Run js-export on the old system
• Install the new one
• Run js-import on the new system

That will indeed keep all of your reports, datasources, input controls, etc.

As a quick-fix you can simply replace the old jasperreports*.jar files in WEB-INF/lib with the newer ones. But the full upgrade would be better so that you're on a standard release.

Regards,
Matt

[manshack_one]

One question if I may.

After running the export I'll need to drop the database from my mysql server right? I figure it needs to do this so the 3.7 general release version has a clean database to start off with.

[mdahlman]

Yes, you can drop the old repository database called "jasperserver" and let the installer create a new one. But I generally leave the old database as it is and create a new one. For example call it "jasperserver37". That makes it easy to quickly refer back to the old one just in case. The .war file install makes it easy to configure the name of the repository database.

Regards,
Matt