gludington

I must be using the wrong archive -- in the 3.5.0 packages, I only see an earlier Mondrian jar, and, while I see subsequent 3.5.x releases in svn, I do not see any src archive in the download area or repo that contains the updated mondrian jar. > find . -name *ondrian*.jar ./jasperserver-repo/mondrian/mondrian/3.0.4.11371-Jaspersoft/mondrian-3.0.4.11371-Jaspersoft.jar ./jasperserver-repo/mondrian/mondrian/3.0.4.11371/mondrian-3.0.4.11371.jar which builds, but I am not able to find a jasperserver-repo to build later versions of jasperserver, e.g. the 3.5.1

Apologies for resurrecting an old thread, but I cannot find this artifact either in the shipped src package or in the online repos. Where can it be found, please?

Both the file up at sourceforge and the jasperforge maven repo do not have jars for the 3.1.0 branch. For example, the jasper reports dependencies are: js-pro-3.1 tagged branch <dependency> <groupId>jasperreports</groupId> <artifactId>jasperreports</artifactId> <version>3.1.2</version> </dependency> On jasperforge, the jasperreports jar only is valid up to 3.0.0.1 http://jasperforge.org/maven2/jasperreports/jasperreports/maven-metadata.xml Building from 3.0.0 tagged branches seem to work, but we are running up against a bug in 3.0.0 that appears fixed in 3.1.0. 3.1.0 is a recent release, but is there a possiblity of the jasperforge maven repository being updated to keep in sync, or a new repo archive being made availble for download? Post Edited by Greg Ludington at 11/26/08 20:04

3.0.0 -- I was using the jasperserver 3.0.0 linux bin installer, so every version comes directly from there. I grabbed the 3.1.0 distribution yesterday after it was released, and I do not see that problem with 3.1.0.

I may be missing something simple here, but I am unable to run any of the web services examples. I am running the webapp sample in the same tomcat instance as jaspserserver, and, when I try to invoke a runReport command, I get a NPE with the following stack trace: java.lang.NullPointerException at net.sf.jasperreports.engine.fill.JRTemplatePrintFrame.getTopBorder(JRTemplatePrintFrame.java:136) at net.sf.jasperreports.engine.export.JRHtmlExporter.appendBorderStyle(JRHtmlExporter.java:1278) at net.sf.jasperreports.engine.export.JRHtmlExporter.exportFrame(JRHtmlExporter.java:1878) at net.sf.jasperreports.engine.export.JRHtmlExporter.exportGrid(JRHtmlExporter.java:768) at net.sf.jasperreports.engine.export.JRHtmlExporter.exportPage(JRHtmlExporter.java:673) at net.sf.jasperreports.engine.export.JRHtmlExporter.exportReportToWriter(JRHtmlExporter.java:632) at net.sf.jasperreports.engine.export.JRHtmlExporter.exportReport(JRHtmlExporter.java:371) at org.apache.jsp.executeReport_jsp._jspService(executeReport_jsp.java:99) This might suggest that getBox() is returning null, but I do not see why that would be the case. I am using the 3.0.0 installer of jasperserver, and the sample reports and the java-webapp-sample code dropped into the same tomcat instance. Is there something else I may have missed that is required to get the web services portion functioning properly?

Of course, that was not it..the issue was that the internal openflashchart.xsd was not copied over to the build/classes classpath area that use used by subsequent targets. When I moved that over manually, the template compiled and the rest of the tasks ran.

In evaluating jasper, I saw the openflashchart support as something that could help give a snappier look to charts as opposed to other plugins. However, the schema location http://jaspersoft.com/xsd/openflashchart.xsd shows a 404 error, which renders the templates unparseable. What is the proper URL for this schema? Thank you, Greg